See also: T274236: Have a process to regularly review projects listed on mw:New_Developers, maybe T252147: Improve the new contributor onboarding process

This task is part of a project to establish a formal review process and set of standards for Wikimedia technical documentation. For more information, visit the project page on mediawiki.org

Page

https://www.mediawiki.org/wiki/New_Developers

Notes

Should be updated to include links to wikicontribs and content from https://www.mediawiki.org/wiki/Developer_account. Look into added programming language based browsing

Content outline

• Welcome!
• "How to get started contributing": 4-step process
• "Basics of how Wikimedia software projects work ": Overview of open-source project components (task tracking, code repo, code review, discussion)
• "Choose a software project" (huggle, kiwix, commons app, wiki ed dashboard, library card, pywikibot) - project list to be updated by Developer Advocates in advance of May 2022 Hackathon.
• Other ways to find projects: Outreach programs & good first tasks
• Additional resources
• “General communication tips” (This section is also translcuded on How to be a MediaWiki hacker)

Basic review

• Typos: The page has been reviewed for typos.
• Inclusive language: The page uses non-gendered language and avoids the terms listed in the [[inclusive language]] guide.
• [n/a] Working examples: Commands and examples have been tested or reviewed for accuracy.
• Links: Links on the page work.

Writing style review

• Plain language: The language used on the page is clear and concise. It is free of jargon, idioms, and other ambiguous or confusing elements. Sentences are not more than 30 words in length.
• Positive language: Avoid using negative sentence constructions.
• Active voice: Use active voice, except when diplomacy calls for passive voice.
• Second person point of view: Uses second person ("You" or assumed "You") when addressing your audience. Avoid first person ("I", "we", "our"), unless the page is an FAQ with questions asked from the first person perspective.
• Imperative mood: Uses an imperative mood for most documentation focused on goals or process. Avoid future tense ("will").