David Herman

I added some workaround instructions to the README. I'll leave this bug open and will clean up the README later after IJ fixes their issue upstream.

> Have more general questions on dev/test/debug workflow trade-offs... Honestly, this is a huge weak point in Kobweb at the moment. I just haven't had much time to dwell on...

This was probably fixed by IJ a while ago, but confirmed in IntelliJ IDEA 2022.2.2 at least that this is working.

We now have a spiderweb spinner (yeah, cute, I know). I think we can close this bug in its original spirit (which was more about how before everything would grey...

Keep in mind we will probably want to support variables somehow. We can possibly introduce a CssVariable version for some methods, instead of taking string values directly, though.

Note that we're currently using `{{ }}` for calling Composable code. Maybe we can use the same block for front matter stuff too? `{{ $author }}` for example. Or maybe...

Since we can access front matter in code, it's not critical for this to get into 1.0 anymore. (If anyone has a use case that's critical, though, that I'm overlooking,...

This might have been exacerbated by an internal compiler error with compose, which apparently caused Gradle's -t option to stop working, so when I pressed "Q" to exit the server,...

Maybe the easier bug here is that if the client sees that the server is down (at least in dev mode), it should kill the current page and render something...

This might be possible using a ComponentVariant. Investigating....