You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2019. It is now read-only.
Rachael Phillips edited this page Oct 24, 2019
·
4 revisions
What to do for side nav on shared documentation pages like Global CSS Variables?
They should live in both Core and React. This design solution needs to be determined by EOD today.
Should design pages have a Table of Contents?
The design pages that should have a table of contents: Any of the Usage and Behavior Pages. All Styles pages except Icons.
We should update the Content pages with a caviot. The caviot is we must switch the table of contents of the Style Guide and Voice pages first, so that their table of contents are visually aligned.
The design pages that should NOT have a table of contents: Icons
Should core Misc docs pages have a Table of Contents? What about a Side Nav?
Yes to Table of Contents. Does Misc just mean everything? What do you mean by side nav?
Can there be a way to clearly tell what context you're in?
Design should be determined by EOD, most likely leave design as is.