code-standards

code-standards copied to clipboard

For instance, some Markdown parsers are choking on it, particularly the "box" asides. By in large, it works, just could be better.

rcherny

Track the menu location against the scroll

2

Sort of like a scroll spy thing, but the content is long enough it's pretty easy to get "lost" in the section you're in. It would be nice if even,...

rcherny

We should absolutely be reviewing the **current live docs** vs the **new branch** for _must have_ content. We don't want to get too carried away with the editorial process ...

rcherny

Review the standards doc code against our own standards

2

This speaks for itself.

rcherny

Content: JavaScript

2

Content about JavaScript Best Practices go here For specific edits, please still file a ticket, this is mostly ideas to toss around.

rcherny

Content: CSS Section

7

Notes around CSS Best Practices go here. For specific edits, please still file a ticket, this is mostly ideas to toss around.

rcherny

Content: Markup Section

12

Markup section changes here. For specific edits, please still file a ticket, this is mostly ideas to toss around.

rcherny

Content Edits: General Section

2

Put notes on the general section here. For specific edits, please still file a ticket, this is mostly ideas to toss around.

rcherny

Content (Needed): Responsive CSS/Dev/Design Needed

7

We need to build out a Responsive Design/Mobile/Media Queries section of the document. We have the knowledge, just need to make the points and slap something together. Feel free to...

rcherny

Address Milestones, Versions, and Components in a more intelligent way

3

Near, long term, and future are nice and all, but I'd almost prefer to draw a distinction between the _framework_, the _content_, and the _presentation_. Food for thought.

rcherny