+ @DTorsani-WMF for inclusion in the Codex icon audit/review.

Thank you! I retested the issues and TLDR all looks good ...details below

Latest design review (using wikivoyage):

Just tested on wikivoyage and visual notice on footer LGTM:

Review description	Screenshot
Desktop footer V2022
Mobile footer (Minerva)
Old popup - no longer appearing

In T363484#11015070, @cscott wrote:

Current patch demo is at https://649538b6c5.catalyst.wmcloud.org/wiki/New%20York%20City and is ready for review. I had to make a few tweaks to the design to accomodate the selected backend (posting to a talk page). In particular, I needed to provide a topic for the post and also to inform the user of the page where the message would be/was posted.

In T363484#11015070, @cscott wrote:

Current patch demo is at https://649538b6c5.catalyst.wmcloud.org/wiki/New%20York%20City and is ready for review. I had to make a few tweaks to the design to accomodate the selected backend (posting to a talk page). In particular, I needed to provide a topic for the post and also to inform the user of the page where the message would be/was posted.

Adding @Sarai-WMF in case there's design review needed while i'm ooo until Jul 14 :)

In T363484#10955544, @cscott wrote:

In his review, @Arlolra pointed out that the footer text is not used in the MinervaNeue skin. (I tested every other skin available on patchdemo and they looked fine).

MinervaNeue looks like:

Any thoughts on where the 'rendered with Parsoid' text should go for this skin? I'm thinking in the footer, as another item in the "Privacy policy Mobile view Developers Statistics Cookie statement" list.

In T363484#10937870, @PatchDemoBot wrote:

Test wiki created on Patch demo by RHo (WMF) using patch(es) linked to this task:
https://patchdemo.wmcloud.org/wikis/5ab5d73ccc/wiki/New York (magazine)

In T363484#10932402, @cscott wrote:

Sorry, you'll need the parser migration extension installed, and to have parsoid read views enabled for your account:
https://www.mediawiki.org/wiki/Help:Extension%3AParserMigration
That is installed on beta and testwiki, I believe, so it should just be a matter of enabling parsoid read views in your user preferences.

For patch demo, there's https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ParserMigration/+/1100121 which I think can help, but I haven't tried this myself.

hi @cscott - I can't seem to get the footer notice showing in patchdemo, nor on beta or testwiki. Apologies but are there specific settings I should have made to test on Patchdemo, and/or an article that i should be testing on?

@mwilliams completed draft recos in this doc (private to design mgrs)

In T363484#10887904, @cscott wrote:

@mwilliams anything learned from the "bit of time next week to explore a couple other possible solutions", or is this design ready to implement?

Adding Apps design folks for visibility and coordinating changes on iOS and Android as needed.

Adding @nayoub @mwilliams to clarify if needed that UX recommendation/expectation has been for a modal (pop-up in iframe) rather than a separate pop-up window. Relevant discussions about the modal preference over pop up window on T364939 and T365298

thanks @Bethany - happy to resolve and track next steps in new tasks as you see fit!

In T391861#10744224, @MatthewVernon wrote:

@RHo can you approve this request, please? Once that's done, this request can proceed.

Adding in @Pginer-WMF as the original designer who likely can speak directly on this. IMO ideally we want one icon for alerts and notices per T142981: Provide a single entry point for notification that anticipates the urgency of the notifications received for desktop as well, but until such time that happens if we are collapsing both alerts and notices under the single bell icon on Minerva, it would make sense for the count to be for the combined unread number.

Adding @nayoub @AAlhazwani-WMF as well for visibility and consideration for overall Contributors design strategy. As part of goals of a more unified, simplified UX for editors, a key design exploration is how might the existing Campaign Updates module in the homepage, which only supports 1 spotlight event by a community be revised and updates to incorporate this more comprehensive, discovery-centered list of many events.

Adding @OTichonova to provide details about requirements from Mod Tools side.

In T373204#10579079, @A_smart_kitten wrote:

For the purposes of task management, if the work here isn’t yet complete, should this task be re-opened? (Alternatively, should another task be opened to track the design review?)

Agree, thanks for checking and re-opening until design is complete!

In T365298#10309179, @JTweed-WMF wrote:

Thanks for all the input @Bugreporter @TheDJ @mwilliams @sbassett @RHo.

Authentication domain
The broad consensus is that the domain should be reflective of the actual purpose, which is strictly the authentication part of single sign on (c.f. authorization, user attributes and user management). It should also be as understandable as possible. For me this rules out both account.wikimedia.org and sso.wikimedia.org.

Best practices across the industry appear to favour login or auth for custom domains: Auth0, WorkOS, AWS Cognito, SSOReady, FusionAuth.

Given we can't use login.wikimedia.org as it hosts loginwiki, let's go for auth.wikimedia.org.

Wiki identifier
There is a clear consensus for for using the wiki id as the first path part, as plain text. So let's go for that.

That gives our final URLs the form:

https://auth.wikimedia.org/enwiki/wiki/Special:Userlogin

We'll reflect this change before we push to the test wikis.

hi @KStoller-WMF and @JFernandez-WMF - per comments on T375712#10369822 please consider how this task can be raised in priority for fixing. Thanks!

In T375712#10369775, @kostajh wrote:

In T375712#10369090, @stjn wrote:

The biggest current problem is that the temporary account bar is much, much, much more prominent than frankly more important new talk message notice:

This was supposed to be fixed in T341305: Talk page notification alert bar: revised styling to meet WCAG color contrast AA requirements but then it was untagged from your workboard entirely. I feel like, if the temporary account bar will be deployed in the current design, new talk message notice should be updated to match it. Currently it is a very small bar that does not pass WCAG requirements and can’t be noticed by many new editors, especially IP editors. Its design is also not uniform across platforms. It is a frequent community request that something will be done to fix this and make it more noticeable.

@KColeman-WMF @RHo @Niharika do you have thoughts on this point, or on T341305: Talk page notification alert bar: revised styling to meet WCAG color contrast AA requirements? Perhaps the gray status bar for temp accounts could include some prominent visual indicator that the user has a talk page message?

In T363484#10366111, @stjn wrote:

On most wikis, Parsoid is not the default parser (and probably wouldn’t be for a long time). So for those, having a legible logo that can actually be read in night mode (this one can’t) would be better than having... whatever this is. I do not have an opinion on what German Wikivoyage should do, they probably shouldn’t have the indicator at all, but this change made the indicator completely incomprehensible.

! In T363484#10366113, @stjn wrote:

Also, in night mode, current logo just looks like MediaWiki logo. Which is cool, but it is very hard to understand why MediaWiki logo is in the top right. I’m surprised there isn’t anything about mixing MediaWiki logo like this in https://www.mediawiki.org/wiki/Manual:MediaWiki_logo_guidelines tbh. Parsoid should just use a wordmark, having ‘o’ be the MediaWiki logo is a very old (and bad) logo design practice.

I suppose if this is meant to be temporary anyway and purpose is for people testing who know what Parsoid is and means, there is minimal value in changing to the more legible word logo.

In T363484#10363659, @CCiufo-WMF wrote:

For those wondering, the new logo looks like this: