Thanks, here are a few small updates:

@JoeWalsh sorry for the confusion, I included both as we hadn't decided on a size when I picked up this ticket.

Would we want to run some quick usability testing on this flow? We have testing credits and could easily have 5 users work through the editing flow. I've identified some potential UX issues below, but I'm confident that there would be more we could identify through testing. If we don't want to test now, we can definitely test any future designs with first time editors.

This sounds good to me, although based on this conversation: https://en.wikipedia.org/wiki/Wikipedia_talk:Manual_of_Style/Dates_and_numbers/sandbox it seems okay for us to proceed with BC rather than BCE

@Fjalapeno, agreed. It was a part of the initial design to have the title in the top bar change to the date after the header has been past: https://zpl.io/Z1kVUNo

@Mhurd, ah right, I totally forgot that text sizing is only applied on the article view. Yes, let's not include it here.

@Mhurd we can definitely do 'Dim images,' would it be possible to run a quick review of the string in a couple of longer languages?

Design review notes:

• Add a label to image dimming

If the user switches to dark mode, switches on image dimming, then switches to light or sepia, should the toggle be switched on and disabled or switched off and disabled?

@anyjungleinguy thanks for writing in this feedback and sharing screenshots! I'm curious if you find the 'History' tab helpful for returning to articles you previously searched for or read in the app?

@Volker_E Added the illustration illustration to the Sketch file but will need a bit of time to clean up images for Buttons and Textfields.

Notes:

• Opacity on Darkmode
• Opacity on Sepia (perhaps overlay) would be a secondary priority
• Dimming is disabled on Default mode

I'm open to experimenting with a larger (like Because you read) image, but would like to see if adding the horizontal rules back clears up most of our legibility issues.

@JMinor I spoke too soon perhaps!

@JoeWalsh will we be able to retain the user's selected theme after force-closing the app / the app crashes?

Updated ticket to address potential attribution issues with Share-a-fact.
Please see T170853 for attribution issues related to social (Twitter / Facebook) shares of quoted text.

@Mhurd it's following the same logic as the card action button on the
Explore feed. Unfortunately we aren't able to utilize the filled/empty
state in this menu but I think this is closest we can get to building off
of our existing actions around saving and 'un-saving' something.
Alternatively we can attempt 'un-save' but this would deviate from the
string used for the same action on Explore and as you pointed out would
most likely cause string-length issues.

Ah, good point @Mhurd, we can use the same string as on the feed then 'saved'

Link above goes to: https://en.wikipedia.org/wiki/Hand._Cannot._Erase
Whereas the article URL is: https://en.wikipedia.org/wiki/Hand._Cannot._Erase. (note the last period)

@NHarateh_WMF yes! Looks great!

@NHarateh_WMF Looks great!

@JoeWalsh if this is causing complexity for Reading themes I'm okay with utilizing the default popover arrow.

@RHo thanks for the heads up!

@NHarateh_WMF looking good!

Looks good! Thanks @Mhurd!

Agreed!

For now, surprisingly, I think that using Opacity as the control for image dimming would be my preference. Personally I think it works best across both Sepia and Dark mode and although it does not 'dim' images on Default mode, it does reduce their visual impact.

@JoeWalsh
Suggesting that we turn the text snippet to Base10

@JoeWalsh I wonder also if we want to updated the feed cards to use Base10 #222 for the text snippets on Featured article and Random article cards. As we're using Base10 for the text on In the news and On this day.

I labeled it "secondaryLink" but it's currently only used as a background color. I could update the naming to indicate it should only be used as a background color.

Moving this from Goat on a Train to the Wikipedia iOS App Backlog as the current implementation utilizes a smaller card presentation for 'Read more' articles, which was the primary design goal on iOS. In the future we may want to create a Universal footer design across Mobile web, Android and iOS, but for now this design is sufficient.

Just to clarify, the secondary action color would be used exclusively as a background color?

Try the lightest yellow as a replacement for 'parchment'