-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs/styling guide #588
Docs/styling guide #588
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
422bd88
to
83f22df
Compare
Codecov Report
@@ Coverage Diff @@
## main #588 +/- ##
=======================================
Coverage 77.64% 77.64%
=======================================
Files 43 43
Lines 8006 8006
=======================================
Hits 6216 6216
Misses 1790 1790 |
9175d85
to
26e4623
Compare
…ithout additional effort.
e524687
to
3b2552c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's no small feat to write a helpful, interactive, lean, and comprehensive styling guide for a whole stinkin' lib, killer work @cjpillsbury 🛳️
Co-authored-by: Dave Kiss <[email protected]>
Working version here: https://media-chrome-docs-git-fork-cjpillsbury-docs-styling-guide-mux.vercel.app/en/styling
First pass on a styling guide.
I dropped the external svg example (
<svg><use href="#ref"></use></svg>
) because, although it works, there was not a clean way to include it in sandpack, and the most recent plan (host externally) also has issues.Time permitting, I'd like to also add a section on Styling + WCAG / A11Y, but wanted to make sure we get through any remaining planned updates before expanding on scope even more.