@Pginer-WMF Do you have recommendations how we can give the user 3 options for "view"-ing the article, "creating from scratch", and "creating via CX"? Currently we have them stacked up like below which I'm sure can be improved in terms of usability.

In T118619#1954650, @leila wrote:

@Pginer-WMF Do you have recommendations how we can give the user 3 options for "view"-ing the article, "creating from scratch", and "creating via CX"? Currently we have them stacked up like below which I'm sure can be improved in terms of usability.

Some comments:

• Keeping the button for creation purpose. Instead of combining different kinds of actions (navigation and creation), it may be clearer to keep the focus of the button only on creation actions: "translate" and "create from scratch". In this way the button is providing a default way to create content with access to alternative ones.
• View article. This action seems connected to the preview view that is already showing the article. It may make sense to put it closer to it and present it as "open in new window" or even just an icon (example mockup below).

@Pginer-WMF I'm with you. Thanks for the suggestions.

How do we want to handle the title the new article should have for creation? From my understanding (please correct me if I'm wrong), the link will be something like: https://<target language code>.wikipedia.org/w/index.php?title=<new article title>&action=edit

@schana once the user clicks on "Create from scratch", they should see the following in sequence:

1. A dialogue box that allows the user to enter the name of the article in the destination language, and check if the article already exists. The way CX handles this at the moment is a good example. Check here, for example: https://en.wikipedia.org/wiki/Special:ContentTranslation?from=en&to=ar&campaign=article-recommender-1&page=The_Life_of_Pablo

2. Once the user enters the articles destination title and it's verified that the article does not exist, we should take the user to the following page in the target language: https://<target language code>.wikipedia.org/w/index.php?title=<new article title>&action=edit (which is what you already have figured out :-)

@schana thanks for taking care of this.

I played with a tool a little bit and I have a question/comment:
I choose the source as en and destination as fa, then I choose a recommendation and click on "Create from scratch". I see dialogue box that allows me to enter the article tile, which works great. Once I click on Create, I'm taking to a page that says I need to log in or I cannot create a page in fawiki. When I log in, I should automatically be taken back to the page that I wanted to create, instead I see a 404 File Not Found. Can you look into this?

@leila After clicking the create link, if the user is not logged in there seems to be two options (I was not able to reproduce the 404):

1. Click the login prompt up at the top of the page.
   • For me this took me to the login prompt and, after logging in, back to the create page
2. Click the login prompt within the page itself
   • This sent me to the Main Page after logging in

There is an additional parameter we can add on to the url, redlink=1, which behaves a bit differently.

In T118619#2053071, @schana wrote:

@leila After clicking the create link, if the user is not logged in there seems to be two options (I was not able to reproduce the 404):

This was apparently a temporary site-wide problem. Office had the same problem at that point.

1. Click the login prompt up at the top of the page.
   • For me this took me to the login prompt and, after logging in, back to the create page

Yes. this works for me now.

1. Click the login prompt within the page itself
   • This sent me to the Main Page after logging in

right. it would be good if this would come back to the create page as well.

There is an additional parameter we can add on to the url, redlink=1, which behaves a bit differently.

It looks like the difference is that mediawiki doesn't add the returnto parameter to the link within the "Permission Error" page, but with the redlink enabled it does. Considering it also gives a nicer introduction instead of the aforementioned "Permission Error", I recommend we go that route.

I'm with you, @schana. Do you want to track it in this same task or create a new task for it?

I think this task is fine since it was new functionality within the create from scratch dialog. I've made the change and it's live on the site.

Unless you're talking about the mediawiki issue with the Permission Error page. That should probably be tracked separately.

yeah, I was talking about the Permission Error page. Do you want to create a task for that and put in the backlog for when/if we have time for it? I don't think it's critical to address it, right?