Change 244114 had a related patch set uploaded (by Santhosh):
Set suggestions as active tab for new users

https://gerrit.wikimedia.org/r/244114

A simple check of whether the URL contains campaign parameter is used.

Checking if there is an ongoing translation is the perfect way to determine the active tab. But that is an asynchrounous api call. Swapping the tabs few seconds after page load does not look good.

@Pginer-WMF any smart ideas on this?

A simple check of whether the URL contains campaign parameter is used.

Can you provide more detail on which view will be shown when there is a campaign and which view will be shown when there is none?

@Pginer-WMF any smart ideas on this?

We should definitely avoid sudden changes of the current view. So if we cannot know it in advance, we can try the following approaches:

• Make sure that suggestions are shown the first time ever the user accesses the dashboard. I'm not sure whether that makes things much simpler, but since we are able to show the beta-feature invite once, it may be feasible to use a similar mechanism.
• Facilitate the transition using the empty state. We can adjust the empty state message (T88344#1386908) to indicate there are suggestions, making it easy for the user to access the next logical step. Note that we should show the link only for the languages where suggestions are available (we should avoid telling the user there are suggestions and showing an empty list)

By the way, empty states were not appearing for me. Not sure if there is a bug already about that.

Change 244114 merged by jenkins-bot:
Set suggestions as active tab for new users

https://gerrit.wikimedia.org/r/244114

OK, it works according to Pau's suggestions, though I'm inclined to leave this open to see how it affects the users.

I'm not sure that showing the suggestions tab by default is useful only when users are coming through a campaign.

OK, it works according to Pau's suggestions, though I'm inclined to leave this open to see how it affects the users.

We can do the following:

• Rename the current task as "Tab 'Suggestions' as default in Content Translation" and close it.
• Create a new "Show tab 'Suggestions' when in-progress list is empty", and add it to CX7 further consideration in upcoming sprints.

In that way the scope of what is done and pending seems more clear. Does it make sense?

In T112822#1724813, @Pginer-WMF wrote:

OK, it works according to Pau's suggestions, though I'm inclined to leave this open to see how it affects the users.

We can do the following:

• Rename the current task as "Tab 'Suggestions' as default in Content Translation" and close it.
• Create a new "Show tab 'Suggestions' when in-progress list is empty", and add it to CX7 further consideration in upcoming sprints.

In that way the scope of what is done and pending seems more clear. Does it make sense?

OK. T115458. Feel free to edit.

OK. T115458. Feel free to edit.

That looks good to me.

I edited the description of the current task to specify what has been done. From your comment ("it works according to Pau's suggestions"), I assumed both of the comments I made in T112822#1708124 have been supported. Please, make sure to verify that this is correct or edit accordingly.

Make sure that suggestions are shown the first time ever the user accesses the dashboard. I'm not sure whether that makes things much simpler, but since we are able to show the beta-feature invite once, it may be feasible to use a similar mechanism.

Done, although it also checks for a campaign, and I'm not sure that it's right.

Facilitate the transition using the empty state. We can adjust the empty state message (T88344#1386908) to indicate there are suggestions

Not done, and deserves a separate task.

Done, although it also checks for a campaign, and I'm not sure that it's right.

One way to check is:

1. Create a new account.
2. Enable CX beta feature
3. Access ...Special:ContentTranslation (without any especial parameters)
4. Observe that the view open is "Suggestions"