Important Resources

I am collecting all the important resources here that will come handy during Outreachy project (fingers-crossed)

How to write test cases and where to find the file needed to be pushed on the upstream when any changes are made – As Sebastian Karcher explained,”As for Scaffold, the header is written automatically. You should just save the translator from Scaffold and then open it from its location on the hard disk, i.e. in the translators folder in the Zotero data directory.

The translator tests are created automatically when you click on “New Web” in the “Testing” pane in translator while looking at a relevant page. You’ll then want to click “Save” again in Testing once you have all tests and make sure to save your translator (using the “save” icon at the top of Scaffold).”

Points to keep in mind while preparing a documentation that is effective – Sumana taught me this in one of the English learning sessions, ”

Whenever we’re writing something, to inform or persuade someone, if we’re trying to figure out whether something works or why it doesn’t work, it’s helpful to consider:
1. Audience
2. Medium
3. Message

For each section that I’ll write about the Zotero translators, I can take help of

“Claim, link, evidence.”

Claim – What I want to explain?

Link – What is the need and importance of this particular section in the context of the whole documentation?

Evidence – Any resources for the same (links of translators that make use of this section.)

HWZT – Zotero guide, outdated but still has much to teach –

Common code block for translators -The whole Wiki of zuphilip is interesting, really useful.

Place where I’ll create the documentation – Existing page, I’ll edit this one.

Place to look for tasks, Zotero & External board

Research write-up for translators in other languages

Extension: Translate for Hindi page of documentation

English Wikipedia talk page

About commit messages –

List of fields in all type :