@Volker_E I had imagined something like this (perhaps with the list items rearranged):

another alternative:

I agree that we should increase to 12pt

Checked this out and it looks good. I've added T237019 as a subtask to this and think we should address the spacing issue there.

In T211006#5630616, @Trizek-WMF wrote:

Have you considered to add a link to an help page that would provide best practices to create articles?

In T237561#5642698, @Niedzielski wrote:

@alexhollender, is it important to represent this new setting as a suboption?
...
I haven't looked yet but it may be easier on the tech side to move to the top level so I was curious.

In T236328#5641344, @Volker_E wrote:

How's the behavior on tablet? Same?

In T236328#5637075, @Jdlrobson wrote:

Does this need more discussion or can we go ahead with the original plan (note we can always do follow ups - that patch is pretty small)

I agree with T235737#5639644. Here are two ways we could do that:

In T237230#5637304, @Masumrezarock100 wrote:

That's definitely not the Watchlist page. :-)

@Jdlrobson where are you seeing this? Here is what it looks like for me on Watchlist:

iOS / Safari	Mac / Chrome	Android / Chrome

There have been complaints about the size of links and how close together they are (see T237204) so theoretically this could help with that. Increasing the font-size seems worth considering as well.

If possible links to sections or footnotes within the same page should not open in a new tab.

@Masumrezarock100 thanks for creating this task

In T236176#5595572, @ovasileva wrote:

@alexhollender - seems like we have two options for logged-in users at least - display a modal that confirms they want to opt out and turn it off via the modal, or navigate them to their preferences page where they can turn off the setting. I think the first one is probably better, but the second option is what we use for page previews. Thoughts?

@nray and I just reviewed. Remaining items:

• move Add discussion button to top of topics list (or create a second button there)
• fix View as Wiki page button to bottom of viewport
• add Active discussions header to top of topics list

Looks good to me

Since we've already broken up the text-blog as it appears on desktop I think we should continue on and put the username on its own line

In T226562#5617177, @Jdlrobson wrote:

What about the download link on Chrome?

@Masumrezarock100 @Uostofchuodnego my apologies for the problematic SVG and the delay in responding (I was having a difficult time figuring out what the issue was). I think the issues are fixed now, can you please take a look at this SVG:

@Jdrewniak and I looked at this together — looks good. Any ideas how we want to do QA?

@Masumrezarock100 apologies here as well. I believe this is fixed now:

In T225127#5599893, @Jdlrobson wrote:

@alexhollender stray semicolon is tracked in T233649
There's no bug for the new line but if you want it, you can make one...

Noting that this issue is also present on Watchlist in Advanced mode (https://en.m.wikipedia.beta.wmflabs.org/wiki/Special:Watchlist?hidepreviousrevisions=1&hidecategorization=1&hideWikibase=1&limit=250&days=3&urlversion=2)

In T235690#5596039, @Jdlrobson wrote:

The page is the same as the one on desktop. How should this new line appear on Vector?

Updated SVG
width = 77px
height = 22px

I've checked in with the design team about how we usually create these. Here is an updated SVG to use at the proper dimensions:
width = 118px
height = 22px

@Jdlrobson we discussed this yesterday in kickoff and identified it as a potential iceberg situation. It sounds like this is the right solution but it's not clear that it's worth taking on this work right now. Also to clarify, this task is about the container that notifications get rendered in. There are two other tasks about the styling of the notifications elements within that container (T225535 and T228819) which I've just made children of this task.

awesome, all set

@Jdrewniak it's kind of difficult to say which option is better until we see how long some of the strings are. If they are rarely long enough to warrant the truncation I think that works fine, however if the majority of the time they're getting truncated we should go with the underneath approach. Perhaps we move forward with the truncation approach for now and then revisit this down the road if we see that they're often being truncated?

In T235416#5576757, @Jdlrobson wrote:

What is the goal of this task @alexhollender - what do we want this to look like? Do we want to remove the dots or simply align them properly?

checked on beta...

I've created tasks for the two current issues. Moving this along.

In T232734#5575398, @Jdlrobson wrote:

This task is about removing that screen altogether by making logout a single click. This screen is a regression from a chance in core that we've never prioritised and the fix is pretty straightforward.

For clarification are we talking about this screen?

Great catch @Aklapper

Thanks for your comments @Volker_E @RHo. Your points on the shortcomings of the demo are noted, though just as an FYI it did perform well during our user research.

T216789 suggests expanding all sections by default which adds a new dimension to how we go about solving the in-article navigation problem. Depending on how important we view that need it would be necessary to re-evaluate potential solutions here.

In T191176#5573543, @Masumrezarock100 wrote:

@alexhollender Don't you think the logo's color should be #54595D instead of pure black?

In T234550#5567642, @Volker_E wrote:

@Krinkle has provided a different idea in a conversation today, that I think is worthwhile considering over the mirroring I've provided above.
transform: scale( -1 ) scale( -1 );
https://usercontent.irccloud-cdn.com/file/Bw0Ow2hV/Untitled2.mov

I created a demo to explore the proposal of rendering all sections open by default, while providing a new table of contents mechanism: view demo here. Some tradeoffs worth considering:

@Jdlrobson @nray here's what I'm seeing:

In T191706#5563190, @Jdlrobson wrote:

I dont think this is blocked on anything. If so, what?

In T230016#5557333, @pmiazga wrote:

@ovasileva, @alexhollender
Is the Advanced mode provides improved access to talk pages, history pages, user tools, and other editing tool. message final?

In T218451#5557161, @Volker_E wrote:

I think this is “resolved” now, correct @alexhollender? :)

Spoke with @Volker_E and we agreed to remove the flip/spin animation but keep the color change. Also noting that it would make sense to remove the spin animation from Vector as well for consistency, but that's not a blocker here.

In T234278#5554202, @Masumrezarock100 wrote:

I can work on the SVG file. @alexhollender should the new logo use #54595D instead of #464646 like the English wikivoyage logo?

@Waddie96 good catch. @Volker_E I think a small improvement would be for the star to flip and then change color. Currently it changes color then flips, which feels a bit off.