govuk-frontend VS Water.css

It depends on the level of contribution.

You can contribute by responding to the discussions in the backlog[0], by improving the actual distributed styles and code[1] or suggesting improvements to the documentation in the link I posted above.

Bigger changes need to be backed up with user research, evidence of user needs and accessibility reviews and checks.

[0] https://github.com/alphagov/govuk-design-system-backlog

[1] https://github.com/alphagov/govuk-frontend

However looking at the samples with modern browsers I was unable to see the overflow issue. So it might now be entirely possible that setting negative margin is not required anymore. And it happens to actually be harmful: negative margin can change the reading order in VoiceOver!

It's quite literally open source, with a permissive license. It's often more than just inspiration, it's the literal code.

Check it out: https://design-system.service.gov.uk/ and: https://github.com/alphagov/govuk-frontend (MIT license)

For those who may be interested, the front end is actually open sourced for third parties to use.

To that end, we're still in the process of dropping support for IE 8–10, along with reducing IE 11 to 'functional'—it doesn't always look the same, but users can still complete tasks.

They're also looking to reduce support for IE11:

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)