Page MenuHomePhabricator

Deploy Growth features on Turkish Wikipedia
Open, MediumPublic


The community consensus is here.



Help panel

  • Provide the URL of your help desk and the page title = Danışma masası
  • Explain how your Help desk is archived = Manually
  • Provide the 5 most important help pages newcomers should have access to, and the label people will read (for instance "how to add an image"). =
  • On which namespaces the help panel will be displayed (0 is mandatory) =
  • Which namespace(s) the Help panel Search should search on? =
  • What is the wikilink to the main help page? =


  • Provide the URL of your tutorial about editing and the page title =


  • Create if necessary or update the mentors list
    • the format is [[User:Name]]|Description (be careful about the position of the | in the example!)
    • add the following sentence at the top:

Please introduce yourself in a short way (240 characters max) so that newcomers will know more about you. To increase focus, your message will not render wikitext or links. [[mw:Special:MyLanguage/Growth/Communities/How to introduce yourself as a mentor|See examples and best practices.]]

  • Provide the homepage mentors list title =

Understanding First Day

  • The list of namespaces where page title will not be recorded for privacy reasons (namespaces 0, 1, 6, 7 are mandatory). =


Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 22 2020, 7:10 PM
Trizek-WMF moved this task from Inbox to External on the Growth-Team board.

Superyetkin, thank you for creating this task! I'm here to help you, so please tell me if you have any questions or blockers.

We are also really happy to see your wiki joining our project!

Trizek-WMF renamed this task from Deploy Growth features on trwiki to Deploy Growth features on Turkish Wikipedia.Jan 23 2020, 12:56 PM
Trizek-WMF triaged this task as Medium priority.

@Superyetkin, any updates on your side?

Is there any chance we can have the features deployed before completing the translations? This may take a while on our side.

Translate the privacy statement, the privacy policy and the interface is mandatory, and quite the rest is too. I'm afraid that the only thing you can skip is the documentation.

These features will be displayed to people who don't necessary speak English. Have English displayed may block them from editing.