Page MenuHomePhabricator

Homepage: addition to main page
Open, Needs TriagePublic

Description

The objective of this task is to help more newcomers discover their homepage. When it is built, it should be part of the "homepage treatment", meaning that those newcomers that are in the treatment group of the homepage experiment should see this addition, and the newcomers in the control group should not.

According to the EditorJourney research, about 45% of newcomers view the Main Page (e.g. https://cs.wikipedia.org/wiki/Hlavn%C3%AD_strana) on their first day (in Czech and Korean Wikipedias). The content of the Main Page is likely not user to a newcomer trying to edit for the first time. We could add a card, link, or message to Main Page saying something like "Click here to view your homepage and get started".

For whatever we design here, we will also need to consider if/how there can be a corresponding mobile design.

Event Timeline

MMiller_WMF reassigned this task from Cntlsn to Catrope.May 8 2019, 10:29 PM

@Catrope -- I'd like to ask you to fill us in a bit on some of the technical constraints here. I know that the main page is a wiki page administered by each community. And I also know that the mobile version of the main page has some logic that picks up parts of the main page and shows them on mobile.

Could you help us think through what kinds of options we have here for giving the homepage some kind of link or affordance on the main page? Would we need to ask communities to change their wikitext (perhaps by including a template we design)? Would it be possible to conditionally show such content only to newcomers in our treatment group? Or would it be possible to build some sort of card that displays at the top of the main page above the community-administered content?

We have three main options:

  • A: Put something in the "chrome" area of the page (the upside-down-L-shaped area along the top and left edge of the screen), which includes the sidebar, personal links and tabs along the top
  • B: Put something in the "sitenotice" area, which is where site notices, central notices and fundraising banners go
  • C: Put something in the content area of the main page

Options A and B can be done by us, in software. Option C requires working with the community to edit the Main Page on-wiki. We can then add a CSS class to the page from software that indicates whether the user has the homepage, and the community can write on-wiki CSS (or we can write it for them) that shows/hides the homepage-related content based on that.

cc @Urbanecm who is likely to have thoughts on this as well

Catrope added a comment.EditedMay 9 2019, 7:15 PM

The "sitenotice" area mentioned in option B is where the Wiki Loves Earth banner is in the screenshot below. If no banner is shown, the sitenotice area is empty (so not easy to point out in a screenshot), but it still exists and we can put stuff in it.

The "content" area is everything below and to the right of the "Vítejte ve Wikipedii" box, and the "chrome" area is everything that is not the content area. As a rule of thumb, if you visit e.g. cswiki with your user language set to English, everything that's in English is chrome/interface, and everything that's in Czech is content.

We have three main options:

  • A: Put something in the "chrome" area of the page (the upside-down-L-shaped area along the top and left edge of the screen), which includes the sidebar, personal links and tabs along the top
  • B: Put something in the "sitenotice" area, which is where site notices, central notices and fundraising banners go
  • C: Put something in the content area of the main page

Options A and B can be done by us, in software. Option C requires working with the community to edit the Main Page on-wiki. We can then add a CSS class to the page from software that indicates whether the user has the homepage, and the community can write on-wiki CSS (or we can write it for them) that shows/hides the homepage-related content based on that.
cc @Urbanecm who is likely to have thoughts on this as well

Thanks for ccing me. I personally vote for similar solution you chosed for user pages. For homepage-enabled users, the main page title will show Special:Homepage, and allow the user to switch back to the homepage. It can look like this:

That's similar to C from your commit, I think.

If you don't want to propagate homepage that much, we can go with a guided-tour-like "banner", something like this can be shown to the newbies:

This one can be shown at every page, not necessarily the main one.

What do you think, @Catrope and @MMiller_WMF?

Why limiting that call to action to homepage only?

Do we know if people are going to the home page because they have some special links there, or because that's the default place to go?

Cntlsn claimed this task.May 23 2019, 1:02 PM

@Urbanecm -- thanks for the thoughts and images. We're definitely going to keep the homepage in the "user space" for now, instead of being an additional tab in the "mainpage" space (like in your drawing). And your idea of a Guided Tour to point newcomers to the homepage is something @Cntlsn is looking at in T222852, because we would hook that Guided Tour to the account creation workflow.

The idea is that we already located the homepage in a place where a lot of newbies go (their user space), and now we are going to other places they frequently go (like the Main page) and giving them indications so they can find their homepage.

So for this task, we're wondering what you think about for the three options (A, B, C) that @Catrope described in his comment. Which do you think would work best to tell the newcomers that their homepage exists?

JTannerWMF moved this task from Needs triage to Triaged on the Mobile board.Jun 12 2019, 2:42 AM
Cntlsn moved this task from Blocked to Backlog on the Growth Design board.Jun 12 2019, 7:03 AM
Cntlsn moved this task from Backlog to Blocked on the Growth Design board.

We've decided we're going to put this on hold until some of the other features to aid discovery are released and we see how users interact with them. We're not sure if the ideas described here are redundant or conflicting with work in T222852.