Water.css VS stampino-element

Thank you!

In the beginning, I used kognise'z water.css [1], so most of the smart decisions (background/text color, margins, line spacing I think) probably come from there. Since then it's been some amount of little adjustments. The font is by Jean François Porchez, called Le Monde Livre Classic [2].

I draft in Obsidian [3] and build the site with a couple python scripts and KaTeX.

[1] https://watercss.kognise.dev/

[2] https://typofonderie.com/fr/fonts/le-monde-livre-classic

[3] https://obsidian.md/

Thank you!

I must give credit to Kognise though, the style is simply their formidable water.css layout. It saved me a lot of time and anguish when I was about to get my blog started.

https://watercss.kognise.dev/

https://watercss.kognise.dev/ I would argue classless css is the way to go, you just include a single css file, then write your html without touching any css anymore, all related tags in html are inherently css-ed for you. a nice trade off for me sometimes.

Like the previous submitter ( https://news.ycombinator.com/item?id=30885700 April 2022 ) I found clasless.css while investigating semantic html-oriented css libraries and this one stood out to me as having a good balance. I'm not ideologically opposed to using classes, but using them for every bit of styling seems off and I'd rather see good default styles for regular semantically structured html. For example, classless.css uses the "card" class for cards which don't have a clear analog in among standard html tags: https://developer.mozilla.org/en-US/docs/Web/HTML/Element

Other libraries:

Water.css: https://watercss.kognise.dev/

MVP.css: https://andybrewer.github.io/mvp/

Missing.css: https://missing.style/

WaterCSS, very basic but good-looking UI in my opinion

Slap this on it and you're good: https://github.com/kognise/water.css/

- https://watercss.kognise.dev/ Small size (< 2kb)

As someone who helped lead the Polymer team in the transition from HTML-first Polymer to JavaScript-first lit-html/LitElement, I have some experience building approaches.

I think that JavaScript-first is far better for templating the more general case (or the lower level foundation) because JavaScript is where your data lives. It's generally much easier to bring markup into JavaScript than it is data and data manipulation into HTML.

In HTML you need re-invent expressions, scopes, control-flow, references, and imports. You're going to spend more time and code implementing a less expressive, slower, and more proprietary system.

In JavaScript you just need a way to describe fragments of the resulting DOM (whether you prefer JSX, function calls, or tagged template literals), and the rest is just JavaScript.

Now, I do see benefit from the HTML-first approach for a lot of people and some use cases. One reason I also push on web components so hard is that with interop comes flexibility in allowing a mix-and-match of approaches. As a side-project I'm working on an HTML-first declarative component system layered on top of LitElement: https://github.com/justinfagnani/stampino-element