Hey, side note: we probably want to center this out before releasing to end users.

@Samwalton9-WMF I have added an optional config value $wgPersonalDashboardBlueDotMinimumEdits (default 100, per acceptance criteria) for testing purposes.
Do you think this would be a useful feature to expose as a CommunityConfiguration option as well?

In T410036#11530297, @Kgraessle wrote:

Hi, I had a question about the non advanced mode designs.
On the patch demo above when I do not have ACM I see the following:

Which is a bit confusing to me as the blue dot is now in both places and the left hamburger menu doesn't have anything to do with the Dashboard, unless I'm missing something?

It looks great on desktop, and ACM mode though!

Also a design question around the disappearing behavior, in the acceptance criteria it says:

Users see the blue dot until they click through to the Extension:PersonalDashboard.

Does this mean that the dot shouldn't appear again after a user has viewed the PersonalDashboard, because currently the dot disappears but if you go back to the home page it appears again.

@Samwalton9-WMF We need to reach out to thwiki for their feedback on the threshold.

In T412139#11514832, @Volker_E wrote:

While I'm still not a proponent for the different button sizes*, it seems only congruent to feature the same sizes for the same button appearance. @Dillon Just to be clear, there's not a stated product need for the applying a ToggleButton in a different size though?

• As the guidance on when to use which is quite loose, possibly adding to more confusion and more usability issues than better user workflows.

Hi @Kgraessle, great work so far! Just a few nits:

In T402782#11430504, @OTichonova wrote:

3. The header on mobile doesn't fully match the designs.
4. The back arrow should is smaller (16x16pts)
5. The margins for the header should be 8pts
6. The margin for the content is 16 pts
7. The title is Heading 4 (bold)
8. The padding around the title is too large. Header height is 46pts
9. The dividing line is missing between the header and content on the page

Stalling for now, as we need to do a bit of overhauling to the extension core in order for the mobile navigation to behave like the Figma design:

In T402782#11430504, @OTichonova wrote:

Hi @Dillon! This looks great I had a couple comments/questions

1. The size of the title in the examples (eg. no original research title). It looked bigger than the mocks and when I pulled the codex component, I realized that the title should be smaller. In Figma it is "Heading XS/Bold with font size 16, line height 20.

2. I had a question, on mobile it looks like the examples are taking up the full screen width while I Figma the aren't, I saw that if the width of the screen is increased they change but was just curious if that is the expected behavior?

3. The header on mobile doesn't fully match the designs.
4. The back arrow should is smaller (16x16pts)
5. The margins for the header should be 8pts
6. The margin for the content is 16 pts
7. The title is Heading 4 (bold)
8. The padding around the title is too large. Header height is 46pts
9. The dividing line is missing between the header and content on the page

Quick note: The mobile popover will look different between screenshots and web. This is expected behavior, as Figma typically gets features first before they're implemented in Codex (see T386144)