Heydon Pickering

Offer the ability to show Github issues corresponding to patterns/documentation end points using Github's API.

Some examples: Checking for role="main" / on #main... ``` css #main:not([role="main"]):not(main):after { content: 'error message'; } ``` Checking for role="banner" on page-level header: ``` css body > header:not([role="banner"]), #header:not([role="banner"]), #page-header:not([role="banner"])...

Revert "Clarify the keyboard focus warning"

4

Reverts Heydon/REVENGE.CSS#7

Use `aria-labelledby` with space separated "group-label-id label-id" :-(

Distribution

1

Get it on npm, unpkg etc.

Currently, references are resolved by finding and applying the true value. ```json { "token-1": "#fff", "token-2": "{ token.1 }" } ``` ...results in this Sass: ```css $token-1: #fff; $token-2: #fff;...

Turn off warnings as well as errors?

4

The warnings for missing assets are quite verbose. Can I have a way to turn them off? Or is there a way already?

[] Add note to playbook [] Cite WCAG 1.4.1 [] Open to review by people who attended the open-space discussion

content property block

3

Because you can't style pseudo-content without declaring `content` innit.

Stringified override options don't parse

5

Hi! So far so good, except when I pass the JSON string in your example, the template no longer parses (`Having trouble writing template: docs/components/card/index.html (TemplateWriterWriteError)`). Any idea what that...