Page MenuHomePhabricator

Create project page for Automatically suggest categories when creating a new article
Closed, DeclinedPublic


Hello genie, thanks for signing up to fulfil a wish! This Phabricator card will help you create a new project page for the proposal you are fulfilling.

Per Community Tech procedure, once a proposal has been approved for development, you need to create a project page to provide basic information about it.

Here is some guidance:

  • Next, add an infobox by copying and pasting the wikitext below unto the new page you are creating. In the infobox, only complete/add a value to the name parameter by insert the name of the wish there.
{{Wikimedia engineering project information
|logo        = 
|wishlist    = yes
|name        = 
|description = 
|start       =
|end         =
|group       = {{pg|Community Tech}}
|lead        =  
|team        = 
|phabricator = 
|updates     = 
|previous    =
|next        =
|projectpage =
|display     = {{{display|}}}
  • Next, it's time to briefly describe what this proposal is about. Share the proposal's name; if it has been renamed, please indicate it so others are informed. Include how the proposal ranked in the survey. Describe what problem the proposal seeks to solve. Provide links where necessary. See an example below:

The Edit Recovery feature (previously known as the Auto-save feature) was the #8 wish in the Community Wishlist Survey 2023. This feature saves wikitext and other edit form information while typing, and allows for restoring it after the browser has been accidentally closed, or a power or network outage or browser crash has happened. Requests for this functionality have been made more than once.

  • The next thing is to state the purpose of the new project page. Copy and past the boilerplate text on a new line:

This page outlines Community Tech's approach to addressing the needs expressed in this wish's proposal, as well as considering previous discussions around the request.

  • Lastly, review your work, and publish the page!

Note: Should you have an update to post during the hackathon, please go ahead and add it to the page you have created. Since updates vary, the most important thing is to use sections to share them.

Here are some examples of sections and their headers for various updates added to pages during the development of a wish. Please let the section titles reflect the kind of update you are giving. See examples below:

== Implementation options ==
== Legal considerations ==
== Design updates ==
== Investigations ==
== Project Status Updates ==

And so on.

Thanks for volunteering to do the documentation!

Event Timeline

Aklapper added a subscriber: srishakatux.

@srishakatux: A good first task is a self-contained, non-controversial task with a clear approach. It should be well-described with pointers to help a completely new contributor. Given the current task description pointing to zero information about the project to be documented, I am removing the good first task tag. (Plus I personally don't really understand why to create an empty placeholder page for stuff that happened ages ago - does not sound useful for any reader or like a good use of anyone writer's time.)