Choo VS elm-css

I haven't used elm much, but I do like elm quite a bit! I actually wrote a JS framework inspired by the "elm architecture" a few years back (choo). Admittedly I never looked at how they do CSS though. Is the elm-css package the right thing to look into?

I'm currently working on a way to extend the code by revealing the underlying [Choo](https://choo.io) framework to enable easier hacking! Search is one feature that theoretically won't be too hard to add, but I excluded it from the core because it would have made it too big.

Note: I have no solid reference point for what "too big" actually means for this project—my only guideline so far has been "as small as possible"

I haven't used elm much, but I do like elm quite a bit! I actually wrote a JS framework inspired by the "elm architecture" a few years back (choo). Admittedly I never looked at how they do CSS though. Is the elm-css package the right thing to look into?

Trying to help build a design system at work in my spare time; no clue if it will go anywhere but it’s fun regardless. I asked the Elm Slack group what the equivalent of React Storybook. Specifically, I wanted a way to build a documentation website like Vuepress with the ability to host native Elm code to showcase components. They pointed me to Elm Book. While Elm Book has built-in theming capabilities, I needed CSS control over my components. While they support elm-css, I wanted the ability to use TailwindCSS. The Elm libraries haven’t kept up with Tailwind’s changes, which is fine; writing raw Tailwind CSS on Elm HTML functions is easy and co-located with the component you’re styling.