Page MenuHomePhabricator

Re-think the organisation and the structure of the Growth pages on Mediawiki
Open, MediumPublic

Description

While Growth wants to scale to more wikis, we need to review how the root page and its sub-pages are structured and organized: https://www.mediawiki.org/wiki/Growth https://www.mediawiki.org/wiki/Help:Growth

The goal is to have a hub, where people can find information about the tools and the projects.

Plan

A possible plan would be the following (to be discussed and refined):

  • the tools we offer to deploy on their wikis
    • description of the tools
    • metrics about their efficiency
    • how to get them
    • ressources on how to use the tools
      • for experienced users
      • for newcomers
  • team's goals
    • the current projects we are working on, so as the project pages
      • project updates
      • current project pages
        • past project pages as a sub page
      • the team
  • newsletter

Text

  • Preserve as much existing text as possible
  • Switch from "experiments" to "features"

Compatibility

  • Pages must be compatible for a display on mobile and desktop
  • Pages have to be designed for long-term purposes, since the features will be default ones at some point

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Trizek-WMF triaged this task as Medium priority.Nov 18 2020, 9:48 PM

Hi, regarding the Mediawiki page of the Growth Team, I have a few ideas:

  • I think we should think about writing a lead paragraph for the page. It could be short with only information about the team's main goal and main projects we are focusing on to reach that goal. Because the "Objective" heading are too long and detailed and (imo) written in a story-telling style, people may find it difficult to actually grasp what we are doing - they may eventually understand our goal, but it feels hypothetical; and people can hardly figure out from the "Current initiatives" which prjs are our most focused ones.
  • We are working only on the homepage so perhaps it'd be better visually to add a screenshot of the homepage and say "all our top features show up here".
  • The "past prjs" heading should be somewhere at the bottom of the page (because it's in the past).
  • Shouldn't the "objective" and the "goals and metrics" heading stay close together? Or maybe merge into one? (the "goals and metrics" still say that we have only 2 target wikis).

Hello everyone!

I think we should ignore our previous "super-projects", like "Personalized first day". Those were great names for making it clear what kind of things we would like to do, when we were not sure what we should do to make newcomers more happy. Now that we are more certain about that, I think we should move those super projects (like https://www.mediawiki.org/wiki/Growth/Personalized_first_day) to archive, and instead create top-level pages about each long-term project we maintain, like https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage would become "Growth/Newcomer homepage". That way, people interested in the history of Growth team would be able to still read those historical info, but since most users want to know "what happens now", it would be more meaningful page structuring.

We should also move pages about individual projects (like experiment results, analytics report, or community consultation pages) as subpages of the project they relate to, so people would have a chance to read "everything related to the homepage", for instance.

Does this make sense, @Trizek-WMF?

Thank you for your feedback.

  • I think we should think about writing a lead paragraph for the page. It could be short with only information about the team's main goal and main projects we are focusing on to reach that goal. Because the "Objective" heading are too long and detailed and (imo) written in a story-telling style, people may find it difficult to actually grasp what we are doing - they may eventually understand our goal, but it feels hypothetical; and people can hardly figure out from the "Current initiatives" which prjs are our most focused ones.

Good point. Concerning lead paragraphs, I think we should have a proper introduction for each tool, with links that go to detailed information. This introduction should be like a Wikipedia article intro: a way to understand everything about the topic in a few lines.

  • We are working only on the homepage so perhaps it'd be better visually to add a screenshot of the homepage and say "all our top features show up here".

At the moment we are, but what about in the future?

  • Shouldn't the "objective" and the "goals and metrics" heading stay close together? Or maybe merge into one? (the "goals and metrics" still say that we have only 2 target wikis).

Good question. Maybe have objective and goals, and then metrics.

Hello everyone!

I think we should ignore our previous "super-projects", like "Personalized first day". Those were great names for making it clear what kind of things we would like to do, when we were not sure what we should do to make newcomers more happy. Now that we are more certain about that, I think we should move those super projects (like https://www.mediawiki.org/wiki/Growth/Personalized_first_day) to archive, and instead create top-level pages about each long-term project we maintain, like https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage would become "Growth/Newcomer homepage". That way, people interested in the history of Growth team would be able to still read those historical info, but since most users want to know "what happens now", it would be more meaningful page structuring.

I totally agree about the super-projects pages. concerning archiving, this is something that has to be carefully considered, given the fact that these pages are the roots of these projects.

Does this make sense, @Trizek-WMF?

Yes, thanks!

My thoughts so far are:

  • we need to keep things very simple, focusing on an audience that don't speak English naively, and who is just curious about the tools
  • we need to frame things so that communities would like to get our features
  • we need to think about these pages as a long-term project. The features are successful, and they are very likely to be deployed everywhere. Documentation and information should then be resilient to long-term usage.

Here are my thoughts:

  • I think it is probably too difficult for people to find the pages that are the ones that are active right now, i.e. to see what which projects we're focused on at this time.
  • I'm concerned that some of those project pages are nested too deep, i.e. /Personalized first day/Newcomers tasks/Structured tasks/Add a link. This reflects that we have changed around the way we think about our projects, and we should untangle it. For instance, the "personalized first day" concept is no longer part of our planning.
  • I like the way we post updates: having one update page with all the updates.

[...]

I think we should ignore our previous "super-projects", like "Personalized first day". Those were great names for making it clear what kind of things we would like to do, when we were not sure what we should do to make newcomers more happy. Now that we are more certain about that, I think we should move those super projects (like https://www.mediawiki.org/wiki/Growth/Personalized_first_day) to archive, and instead create top-level pages about each long-term project we maintain, like https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Newcomer_homepage would become "Growth/Newcomer homepage". That way, people interested in the history of Growth team would be able to still read those historical info, but since most users want to know "what happens now", it would be more meaningful page structuring.

I totally agree about the super-projects pages. concerning archiving, this is something that has to be carefully considered, given the fact that these pages are the roots of these projects.

I don't agree that they're root of our projects anymore. They're historically, but I don't personally use the names of that super-projects anymore when talking about Growth features (unless someone's curious in wiki-history). So, I think their content should be made an archive-like page.

I was thinking about whether it will be suitable to create the help page (or any other relevant section) as a virtual tour format. For example, like this one: Introduction to referencing with VisualEditor. In that case, it will be more convenient for the readers to get acquainted with different works or projects of the growth team. We all know that readers feel more motivated to read thoroughly and engage accordingly if it is presented in an attractive way. Mostly current projects/features should be listed there as they will be germane.

Thank you all for your feedback. I worked on the plan, reorganizing things we already have. The result is there: https://www.mediawiki.org/wiki/User:Trizek_(WMF)/sandbox I let it settle.

Next time (next year), work will be about missing pieces and unnecessary ones (project pages and steps by steps are very interesting leads).