Skip to content

🎨✨ adopting sanitize.css #851

@DerekNonGeneric

Description

@DerekNonGeneric

πŸ› Bug report

Location

Section of the site where the content exists

Affected URL(s):

Description

Concise explanation of the problem

Our number of pages is growing, so we should start thinking about our SCSS architecture and how we intend to decompose everything modularly into separate stylesheets/templates and perhaps rethink our critical CSS strategy. We are missing a critical.css file and a reset/normalization (which we already do w/ normalize.css). A recent improvement has been made to normalize.css named sanitize.css.

Differences

normalize.css and sanitize.css correct browser bugs while carefully testing and documenting changes. normalize.css styles adhere to CSS specifications. sanitize.css styles adhere to common developer expectations and preferences. reset.css unstyles all elements. Both sanitize.css and normalize.css are maintained in sync, but only one would be necessary β€” let's switch to sanitize.css!

Sidenote: critical extracts & inlines critical-path (above-the-fold) CSS from HTML.


  • I would like to work on this issue and submit a pull request.

Metadata

Metadata

Labels

πŸ›„ Status: ClaimedIssues that have been claimed to be undertaken by someone

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions