htmx

If things are coming to native CSS the I think the cool kids use PostCSS - tomorrow's features today.

basically: 
```css
.foo {
  & .bar {
    /* the & is mandatory */
  }
  @nest .baz + & {
    /* @nest needed if & not at start */
  }
}
```

Damnit w3c.. why you gotta do is like that?

as long as the & is at the start we should be good, but i don't know if less handles `@nest`

https://github.com/bigskysoftware/untitled/blob/master/docs/concepts.md

some fleshed out concepts to make sure I'm communicating what I'm thinking properly

> Tabs could be similar defined like so:
> ```html
> <div role="tab">
>   <a href="/foo">Tab 1</a>
>   <a href="/foo">Tab 2</a>
>   <a href="/foo">Tab 3</a>
> </div>
> ```
> We would like to explore using the role attribute for this.
```html
<div role="tablist">
  <a role="tab" href="/foo">Tab 1</a>
  <a role="tab" href="/foo">Tab 2</a>
  <a role="tab" href="/foo">Tab 3</a>
</div>
```

I like minimizing the amount of intervention in vanilla html, but I am willing to listen to reason

a goal here is to keep it as close to vanilla as possible

reason: don't style incorrect aria correctly

the role on the div should be `tablist` or `tabs` or something like that though, that's a typo

`role` is not an arbitrary string, it does stuff. and if you don't put the correct roles on things it will not be recognized as a valid tab list

are we allowed to add our own custom roles? (e.g. card)?

the correct element for a card is usually li, article or section

OK, so we will have a mix of aria support for things defined by them

Do you think we should have an opinionated semantic option for card or a class?

using css to enforce proper aria use is a really powerful idea imo

mvp.css uses `article > aside`, which is very incorrect

Well, we could just say "In our CSS lib, article renders as a card"