@GMikesell-WMF thanks for the detailed observations.

@Djido different wikis have different tolerance level but they mostly agree that 100% machine translation does not constitute the editor's "own work" so it needs to be re-phrased to some degree to be compatible with the content policy.

@Djido the system is reporting that the machine translation generated as a starting point is not sufficiently modified by the editor to be published.

This table contains the entries in the language to domain mapping used by CX and the recommendation api:

I can confirm that the recommendation system is unable to tell that an article exist on nowiki. However, another part of the system (cx server) can tell so it is proposing ways to expand with new sections.

In T391502#10784164, @GMikesell-WMF wrote:

@SBisson I just want to confirm with you if this is what you are looking for based on the gifs below...

@EChukwukere-WMF there are two ways to monitor instrumentation events in the browser:

@KCVelaga_WMF could you please add a new "articleplaceholder" event_source to the schema?

That is, the "New page" option will link to Wikipedia:Requested articles when the page is available, and not show the action when it is not.

@Pginer-WMF I don't know what was going on when I took those screenshots... Here's a new set from the main branch after the patch was merged:

The article topics are shown in the "Adjust suggestions" dialog and are organized by groups. This task is about ordering them alphabetically within their group.

@Msz2001 thanks for reporting.

Dashboard should maintain visibility of recently selected topics/collections to provide quick access to them, even after making new selections.

@Pginer-WMF here's some screenshots from the patch above:

At this point I think it's important that the user understands that their work is not saved and that leaving would result in them losing it.

@SGautam_WMF yes, it took some specificity but this is what it looks like:

@SGautam_WMF it looks like this:

@SGautam_WMF about the button style, you can see the options for OOUI ButtonWidget. The closest is "progressive" but it's not identical. Should we use it as-is or custom style it to be just like your mock up?

In T391500#10737196, @Nikerabbit wrote:

Is T391256: Event Logging: dashboard_open event is triggered multiple times a duplicate of or connected to this?

Add a "+ New contribution" button within the tab showing past contributions on desktop only, ...

@Pginer-WMF FYI

I don't think CX mw.cx.SiteMapper.js is actually a blocker here.

@Pginer-WMF the mockup in the task description seems a bit old. The style of the language selector gives it away. Do you want to update it before I get to far on this task?

Not sure what's going on with the CX codesearch results. compatConfig was actually removed a while back from the source and vite configuration but it is still being outputted in the build. Other than being not needed, does it have any adverse effect?

I've submitted a patch to the first the new instrumentation issues mentioned above and captured in T391500 and T391502. If/when that patch gets merged, the original navigation issue described in this task will be reproducible again.

@hueitan the sequence in your screenshots in the right behavior, not the issue reported here.

I don't see arq available as a language in CX or anywhere in mediawiki-config

What is the future of this task now that the unified dashboard is deployed everywhere?

@GMikesell-WMF About AC4, the "New translation" button can only be displayed on desktop. On tablet and mobile, translation is done section by section so the only valid action at this point is to select the section to translate.

I believe the config change (adding back all the target languages) and deployment we did last week should have fixed this error. Moving to QA

A quick note on the cirrusdoc API prop, it's a debugging interface for the search team and should not be used in a production setting.

Possibly related to T386344: Redirect to the target wiki when accessing the editor since the redirection to the target wiki is not happening the second time around.