Skip to content

Resolve #3521079 "Update base styles"

Closes #3521079

To make Bluecheese similar to current core themes I did the following:

  • Removed the Eric Meyer reset css file and used normalize.css from core
  • basic-elements.css is now no longer compiled from sass and the element order matches the basic-elements.css in Claro. I also cleaned up some misc parts that I did not think we were using.

Figma for reference

to dos:

  • update body and p for default text global sizing (questions in figma)
  • update h1-h6 sizes based on latest Figmas (questions in figma).
  • update code text styles
  • paragraph max widths (questions in figma)
  • rename previous "global" styles to wysiwyg styles
  • add global link styles
  • update global ul and ol styles
  • add paragraph/wysiwyg link styles separately if different I used a global base link style.
  • update numbered and bulleted styles - ul is bulleted by default and ol is numbered by default
  • update default table styles (questions in figma)
  • Review section margins (any known work needed here?)
  • Update WYSIWYG Styles (questions in figma) These are now only applying max width and table styles.
  • determine vertical rhythm (default margins and padding on text elements - question in Figma)
  • Deploy to a test environment where we can copy down a db and review actual pages
  • Update base table styles to reflect new design
  • Add font sizing for 1440 desktop wide breakpoint

follow-up:

  • Add vertical spacing for desktop wide elements?
  • update buttons and form input styles
  • Review colors to see if updates are needed
  • consolidate spacing, container and width variables
  • address grids
  • update breadcrumb styles (if still needed)
  • Review global-elements.css and determine whether those styles should be moved into more appropriate component css.
Edited by Bill Sprowl

Merge request reports

Loading