Scott Embler

I understand your perspective Oliver. It was a trade-off between flexibility or conciseness, and I chose the former under the assumption that users could have complicated formatting requirements that wouldn't...

I'm not sure this would simplify the API. It would be nice to remove the need for a Config object/class, but that's not going to gain much when you want...

I think I understand your goal now. Please continue to refine it. I'd personally keep the distinct `indent(boolean)` and `indenter(...)` methods. I think you can drop the cssMinifier() and jsMinifier()...

In this case no, a method for accept-charset is not generated. We can look at supporting this in the future. For now you'll just need to use `Tag.attr(String attribute, Object...

I've heard good things about htmx. To start I'd look at the `Tag::attr` methods to see if those meet your needs. They'll allow you to add any attribute you could...

I think it would need to be distributed as a separate Jar, and I'd expect there to be many changes under the hood as we progress towards version 2.0.

My initial impression from the htmx docs is that this is heavily focused on getting the correct content for the correct attributes. To that end I'd suggest starting by defining...

Thanks @TareqK ! This looks really nice. I like where you are going with your examples.

This should be possible using the `TagCreator.rawHtml(String html)` method. It will take whatever string you give it and append it directly to the output when it is rendered. Example: ###...

You can specify your pseudo-classes in the usual style tag: ``` html( head( style( "p:first-child { color: blue; }" ) ), body( p("This is some text."), p("This is some text.")...