Page MenuHomePhabricator

[ToC] updates to heading & link styling
Closed, ResolvedPublic2 Estimated Story Points

Description

Description

Apologies for not catching this earlier. As we've begun getting more into the visual design we've realized that as a starting point we should keep all styling as simple and consistent with legacy vector as possible, and then be very intentional and specific about any deviations we make. Following from that can we make the following changes to the ToC heading & link styling:

"Contents" heading

  • reduce to 14px (it's currently 16px)
  • remove bolding
  • change color to #54595d (which is the same gray used for headings in the sidebar menu)

Links

  • all links should be blue (#0645ad) including subheads
  • the active link should be black, and not bold (which matches the color of the active tabs in the article header)
beforeafter
before.png (476×458 px, 83 KB)
after.png (477×448 px, 81 KB)

Event Timeline

Jdlrobson removed the point value for this task.
Jdlrobson set the point value for this task to 2.Apr 26 2022, 5:27 PM

Change 787546 had a related patch set uploaded (by Bernard Wang; author: Bernard Wang):

[mediawiki/skins/Vector@master] Update TOC heading and link styles

https://gerrit.wikimedia.org/r/787546

Will be available for testing shortly on the beta cluster

Change 787546 merged by jenkins-bot:

[mediawiki/skins/Vector@master] Update TOC heading and link styles

https://gerrit.wikimedia.org/r/787546

reviewed on beta...looks great all around : )

"Contents" heading

  • reduce to 14px (it's currently 16px)
  • remove bolding
  • change color to #54595d (which is the same gray used for headings in the sidebar menu)

Links

  • all links should be blue (#0645ad) including subheads
  • the active link should be black, and not bold (which matches the color of the active tabs in the article header)

Screen Shot 2022-04-28 at 5.11.21 PM.png (716×975 px, 243 KB)

@Jdlrobson do you think this need to go through QA? I'm not sure so moving to signoff but feel free to pull it back to QA...

Confirming this is done on the beta cluster. I think we're okay to resolve.