1317230 - Authenticated users should be redirected to their locale home page when opening https://pontoon.mozilla.org/

Status: RESOLVED FIXED

(Webtools Graveyard :: Pontoon, defect, P2)

Description

[Francesco Lodolo [:flod]]

Every time I open https://pontoon.mozilla.org/ I get the page to translate Pontoon's website. Then I either change the project (too many clicks…), or manually rewrite the address to https://pontoon.mozilla.org/it to get the list of my projects

I think it would be more useful to redirect authenticated users to their locale's homepage.

Comment 1

[Matjaz Horvat [:mathjazz]]

Copied from bug 1218801:

--
It's great that Pontoon homepage serves as about and demo page, explaining the basics of the tool and also allowing visitors to quickly test it.

But it also raises a few concerns:

1) Is it smart that we allow anyone to submit all kinds of translations/suggestions to our homepage which is than served to all users of that language?

2) Is it really the best possible homepage for authenticated users, who already understand the tool? Or shall we serve them a project/team/other dashboard instead?
--

I'm not a big fan of the team page being used as the homepage for authenticated users, because that would make the homepage point to different pages for different users. However, many popular sites do that. And if we use redirects, the final URL will still lead to the same page for everybody.

We also need to figure out what team page to show for what user, taking into account permissions and translation submissions, because many users contribute to more than one locale.

Comment 3

[Francesco Lodolo [:flod]]

I still think this is quite a problem. If you land on https://pontoon.mozilla.org/, there's no way to discover either the Teams or Projects page.

If you really don't want to redirect them, at least add a navigation on top to reach those key pages.

Comment 4

[Matjaz Horvat [:mathjazz]]

Ugh, my comment was very unclear. I believe we *should* redirect users to their team page.

The main work here is to figure out the (performant) way of telling what team page should we redirect each user to.

A possible solution with some implementation details:
1. Unauthenticated users and users without any contributions should keep using the default homepage.
2. All other users should be redirected to the homepage of the team they made most contributions to.
3. We should run a daily cronjob to calculate what team has each users made most contributions to.
4. Users should be able to override their homepage in settings.

Another possible solution would be to only offer this option in user settings.

Comment 5

[Francesco Lodolo [:flod]]

> 1. Unauthenticated users and users without any contributions should keep
> using the default homepage.

I was wondering today if we're losing potential contributors this way. They end up in Pontoon Intro, understand that this is a localization tool (hopefully) and not just a localizable website, but don't see any of the projects enabled for their preferred language.

If we keep the current landing page, we need at least to add a navigation menu that makes Teams and Projects pages discoverable.

> 2. All other users should be redirected to the homepage of the team they
> made most contributions to.
> 3. We should run a daily cronjob to calculate what team has each users made
> most contributions to.
> 4. Users should be able to override their homepage in settings.

I would drop 2 and 3, land users to the first available match in accept-languages, and let them customize in 4.

Comment 6

[Matjaz Horvat [:mathjazz]]

(In reply to Francesco Lodolo [:flod] from comment #5)
> > 1. Unauthenticated users and users without any contributions should keep
> > using the default homepage.
> 
> I was wondering today if we're losing potential contributors this way. They
> end up in Pontoon Intro, understand that this is a localization tool
> (hopefully) and not just a localizable website, but don't see any of the
> projects enabled for their preferred language.
> 
> If we keep the current landing page, we need at least to add a navigation
> menu that makes Teams and Projects pages discoverable.

Yeah, I don't mean this specific homepage, but whatever we have on http://pontoon.mozilla.org.

Filed a bug to change the homepage:
https://bugzilla.mozilla.org/show_bug.cgi?id=1378471

> > 2. All other users should be redirected to the homepage of the team they
> > made most contributions to.
> > 3. We should run a daily cronjob to calculate what team has each users made
> > most contributions to.
> > 4. Users should be able to override their homepage in settings.
> 
> I would drop 2 and 3, land users to the first available match in
> accept-languages, and let them customize in 4.

I like that. Should be pretty simple.

Comment 7

[Julen Ruiz Aizpuru]

I'd like to add a +1 to the initial request (I'm not aware of a way to add _reactions_ in BZ).

I would also add that this can be further simplified. At least in Pootle there's no such preference, but it works pretty well because it remembers the last language translators explicitly selected, and this is commonly one language. For the vast majority of translators once they pick up their language from the list, they're all set. Managers will usually land on a specific language of choice or in all languages (/projects/), depending on what they explicitly selected last.

Comment 8

[Axel Hecht [:Pike]]

Here's how that pootle behaviour felt to me: at random points in my work, I got redirected to random pages. Rather erratic behavior that I wouldn't have mapped to the algorithm you described.

Let's not do that on pontoon.

Comment 9

[Matjaz Horvat [:mathjazz]]

(In reply to Julen Ruiz Aizpuru from comment #7)
> I'd like to add a +1 to the initial request (I'm not aware of a way to add
> _reactions_ in BZ).

There's a Vote button above in the Details section. :)

> I would also add that this can be further simplified. At least in Pootle
> there's no such preference, but it works pretty well because it remembers
> the last language translators explicitly selected, and this is commonly one
> language. For the vast majority of translators once they pick up their
> language from the list, they're all set. Managers will usually land on a
> specific language of choice or in all languages (/projects/), depending on
> what they explicitly selected last.

That's an interesting idea, but it might be confusing for project managers (I also count Axel as one of them in this particular case :D), who use various locale pages. If possible, we should follow the "principle of least astonishment".

Also, thanks to jotes we now have a PR ready that allows users to select their custom homepage:
https://github.com/mozilla/pontoon/pull/683/files

Comment 10

[Julen Ruiz Aizpuru]

> Here's how that pootle behaviour felt to me: at random points in my work, I got redirected to random pages. Rather erratic behavior that I wouldn't have mapped to the algorithm you described.
>
> Let's not do that on pontoon.

My point is about when users hit / only (which is what this bug is about).

Without further context I'm not sure what you are talking about when you say being redirected to random pages at random points (FWIW I don't consider / to be a random point). So if I understand your comment properly, I only read an opinion about a past experience, not about what I suggested.

Comment 11

[Julen Ruiz Aizpuru]

(In reply to Matjaz Horvat [:mathjazz] from comment #9)
> There's a Vote button above in the Details section. :)

Oh, thanks! it was hidden by default for me :)

Comment 12

[Francesco Lodolo [:flod]]

(In reply to Julen Ruiz Aizpuru from comment #10)
> Without further context I'm not sure what you are talking about when you say
> being redirected to random pages at random points (FWIW I don't consider /
> to be a random point). So if I understand your comment properly, I only read
> an opinion about a past experience, not about what I suggested.

Since I've experienced the same random behavior as Axel on Pootle: if you work on multiple languages, / redirects you to a language without a clear reason. So, it worked pretty badly for me, even if I'm not the typical use case.

Comment 13

[[github robot]]

Commit pushed to master at https://github.com/mozilla/pontoon

https://github.com/mozilla/pontoon/commit/fa3a396482caed75ebb2d3732b34068eae4b4357
Fix bug 1317230: Enable custom use homepages

Add user setting for a custom homepage, which can be a default Pontoon
homepage or one of the team pages. For existing users, set homepage
to the top contributed locale team page via a data migration.

Also, when user visits the homepage for the first time, we check if the
homepage is not set yet and set it to the top contributed locale team
page if it exists.

Fixed along the way:
* Create shared team selector CSS and JS.
* Add parent class to multiple locale selector to prevent selector
  collision.