@Takot, thank you so much!

Updated to include an example of editing a header

We're still going to show when un edited content blobs exist, but we're not going to give the ability to expand it

Per our meeting: Consider changing the logic to only showing two lines before and after an edit, with the ability to hind and show these lines.

Can't undo modal feels too heavy

Change undo link to a revert icon in the toolbar

@Esanders, Ah sorry to clarify this came up in a design review of the editing toolbar, where I could see this applying, likewise the '<back' status bar button when navigating to an app via search.

Another thing to keep in mind on iOS devices is that there is a shortcut built in to scroll to the top when a user taps on the status bar (https://developer.apple.com/documentation/uikit/uiscrollview/1619421-scrollstotop). Just something to keep in mind with tighter tap targets towards the top of the screen.

@JoeWalsh + @schoenbaechler I've updated the ticket with the two designs and Zeplin links. Let me know if you need anything else or if these need another review cycle.

This is looking great, thanks @Tsevener!

Working well and looking good to me! Thanks @Tsevener!

01) Where does the talk page icon come from? Is it Apple specific? There are “chat bubble” icons in Material Design as well, maybe we can use them on Android.

It's the OOUI icon for 'speech bubbles' so if possible I think it'd be great to use it on both platforms for consistency: https://commons.wikimedia.org/wiki/OOUI_icons#speechBubbles. I believe this is the icon currently being used on Android. Technically we could use the 'UserTalk' OOUI icon, but it is often more closely associated with and used for 'Thanks', so I'd prefer to use the chat bubbles if you're okay with that too.

Based on our meeting today I've mocked up a potential footer on iOS and Android respectively.
@JoeWalsh, would it be okay to use different fonts (SF UI for iOS and Roboto for Android)? And also would it be possible to have slightly different margins and padding based on the standards on each app?

Updated, thanks @Remagoxer!

@Remagoxer yes it was, I just needed to be able to keep track of the child tickets associated with this ticket and both tickets were (I believe) describing the same feature request. We'll be working on this feature soon, so it's helpful to have a single ticket for this work. Feel free to add any information you feel is missing.

Not sure if there are any plans to pursue it on Android. Would love to hear more about the rationale behind the change.

We can definitely keep this duplicated in the footer if needed for now on iOS if Android isn't able to work on page issues quite yet, but the rationale is that a page issue is of optimal utility for readers and editors at the top of the page. Specifically, when the page issue is related to content quality and ditto for disambiguation. Eg. It's best to know that the article is biased before reading it, rather than looking to see if there is an issue with the article in the footer.

@Dbrant and @schoenbaechler, ah sorry to clarify that link leads to the article in Places / Nearby, so I don't think that there's much utility in having it in the footer for Android.

Hi @schoenbaechler, thanks for these mocks!
I've been thinking about potentially trying to remove the 'About this article' section, here is a little diagram I've been working with.

When this is all done, create the patch

Export all with a clear background as SVG
Clean up Sketch file
Add onboarding illos