Hi @Dzahn this is all super helpful. I'm curious about which solutions will allow us to have subpages (apologies if I'm utilizing the wrong terminology, but I'm referring to pages that can be referenced after a / )?

Hi folks thanks for raising this. While we can certainly make a radio button work, I do think that the binary radio toggle for width is a pretty different use case, where you are choosing between two named styles (wide and standard). For the birthday related mode, this would require setting a theme of 'Name tbd birthday mode' and 'Classic'.

Apologies for the delay! As @TLessa-WMF's manager I am happy to approve. Thank you and very sorry for holding this up.

This is helpful and I understand now, thanks @DTorsani-WMF !

Or is the goal for Android to default to Deuteranopia & Protanopia until the diff color themes are introduced?

@DTorsani-WMF curious if the plan is to stick with blue and yellow or update to red and green as is suggested on the MediaWiki Site: https://phabricator.wikimedia.org/T399101 Thanks! Sorry for my confusion

@HNordeenWMF updated to include the lock screen widget :)

@HNordeenWMF I updated the ticket with a design, let me know what you think and I'm happy to make changes as needed.

Hi @Tsevener + @Dbrant thanks for these updates, they look good

@HNordeenWMF Thanks for flagging this. It's not ideal but not something I would hold the release for. Thanks everyone!

@HNordeenWMF Nope! MediaWiki page is published in EN and translation has been requested for the other languages. Thank you!

Sorry to step in here, but I've noticed that the hr below the stats has gone missing which I believe is not up to design spec unless @scblr removed this line in another spec for this page (apologies if that is the case, although I do think the information architecture is clearer with the stats encased in a 'table')

I'll suggest that if we update the colors and keep both Dark and Black, we'll need to make a point to keep an eye on usage and to let Amal know about the change as well since Dark is being used more than Black. As an aside I'm really surprised Dark has greater usage than black due to system settings defaulting to Black (we might also want to change this if we eventually want to deprecate Black mode)

@SNowick_WMF thank you for the data, this is very helpful.

@SChekfa-WMF I think it'd be good for us to look into usage of Sepia before discussing deprecating it (@SNowick_WMF, do we have usage data for our 4 themes across both apps?). I have a vague memory of Sepia adoption being high in some languages on iOS, but I can't track down the data now.

@Dbrant Thanks for surfacing this. I think there is an initial question to be answered around the support of both 'dark' and 'black' modes on the iOS and Android apps.

Worked through this with @Bethany!

Site went live: https://wikimediafoundation.org/wikipedia-year-in-review-2024/

Thanks for the updates! Looking good!

Thanks for the updates! Looking good!

Good to know, I do think it'd be preferred to utilize the non-image variant
as defined in the Figma:
https://www.figma.com/design/RnkoK5dDw3lCOEUooZS4jB/Android-App-Library?node-id=4023-16007&t=Ml3xBo4WATUkozjT-0

Thank you @Dbrant ! Working for me now.
Great work everyone on this screen!

This is looking and working great, thanks everyone!

I didn't test to see if the notification itself comes through, but the mechanics on the results screen look good. Thanks everyone.

Hi all, this is looking good, but when I tap on 'Learn more' nothing happens currently.

Hi folks, everything is looking good here, but I'm a bit confused about why the placeholder image utilizes the beta app icon.

@SChekfa-WMF the line spacing looks a little off to me on this card:

Looks good, thank you all!

@HNordeenWMF these changes look good to me and I've pointed @SChekfa-WMF here from Figma to make relevant copy updates.

@SChekfa-WMF perfect, thanks!

@scblr thanks for doing this audit. To make it easier to compare hex values (which Phab doesn't easily support) I created a Google Sheet to see the proposed Codex colors next to the current app colors.

Thanks @SChekfa-WMF for this ticket. I'm very supportive of adopting more M3 components into the app and would suggest that along with an audit screen by screen, you consider mapping from Android's current component library -- it'd be good to also create heuristics around when current vs. M3 components are utilized and adopted (eg. we have Codex / style guide defined guidelines for typography and colors that will need to be squared with M3)

@scblr please be sure to update the task above to reflect syntax highlighting vs. revision highlighting in this section:

Syntax highlight suggestions

@scblr the headings and titles look good, as well as exposing the account number instead of username, I will defer to @KColeman-WMF for the questions around end session vs. vanish account + auto signing.

Thanks @stjn for sharing your concerns. I'm curious if you could share an instance of a site using Minerva where site specific links are currently being utilized and shown, so that @JScherer-WMF and other folks working on this project can find an optimal solution.

Apologies, @Tsevener these mocks were created before the new profile was created. I'll defer to @scblr, but my guess would be that we wouldn't want to bring back accessing talk page through Settings > tapping Username.

Hi @Hghani, we have one more request to wrap up the year in review work. On the public comms channels (social media) we had shared that there were 76 billion views/readers on English Wikipedia and were curious if there's an update to this number based on the addition of December data.

@HNordeenWMF I think in this case it's okay to use 'Temporary account' or 'Account' for the header as what needed to be replaced was the menu item (which is updated above)

@HNordeenWMF, here is the data from @Hghani:

Hi Fatuma, it's a pleasure having you on this project. I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.

Thank you for your task. An intern has been selected for this project, so I am closing this ticket as 'resolved' as the application period has concluded.