htmx

custom elements should have a dash in their name to avoid conflicts with future additions to html

for js-enhanced custom elements this is actually a hard rule

if we require js, we can add a parent selector syntax too

was hoping to keep it a simple style project, but willing to listen to reason here

I dislike needing to require a css and a js file though

<@!725789255590215732> before going too deep into less, have you considered <https://stylus-lang.com/> ? Been using it myself in production for awhile, its been wonderfully short and succinct to work in.

Its basically if 🐍  and CSS had a baby. By TJ Holowaychuk, the original author of express.js.

looks like stylus is a language, but doesn't provide a classless base?

Yeah. Just wanted to ensure you knew stylus exists before committing. aha.

Also there's quite a few stylus compilers on github, don't have to use the node.js one, but it's nice if you have node installed anyway.

although, it clashes with the implied goal of eventually switching to plain css

Oh yeah, the only reason I bring it up is because I see `less` in there. Vanilla is always good if it's reasonable to use it.

we could also use postcss with plugins that bring future features + other stuff we like

does postcss require javascript of the clients?

but unlike others, it does not define a programming language

there's a plugin that adds spec-style nesting, and another that uses sass-style

do you feel it is a better option than less?

I like the idea of using a future standard