I do very much like that by introducing aria attributes, the CSS reacts to it and styles it appropriately. As opposed to a full-blown react component library which does all of that for you. It would be a good exercise for developers to think aria-first and let the library just help with styling.
Lastly, I think the best part is that this component library has a native sidebar. So many of these I see and they have a nice web page which showcases all the components and I want to replicate their layout and nav/sidebars but they only focus on smaller re-usable components and not the layout. So that's a nice touch, I think. And, as someone who keeps an eye on but doesn't do a lot of frontend, the fact that a sidebar is an aside > nav > ul next to a main just makes so much sense and doesn't have a lot of cruft around it.
As someone who has to deal with both angular and nextjs for different (but overlapping) stacks at work, I find myself increasingly sympathetic to this viewpoint.
[1]: https://nadh.in/blog/javascript-ecosystem-software-developme...
Discussed at the time:
And just to be clear, I was poking fun at this so called “CTO”. That guy should have known better.
I see many web/ui frameworks posted in HN which don’t test in older browsers but still claim to be minimal or plain.
Bravo to the author, keep at it. I'll be recommending this to anyone who will listen.
- water.css https://watercss.kognise.dev/
- magick.css https://css.winterveil.net/
- mui.css: https://www.muicss.com/
- pico.css: https://picocss.com/
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
https://oat.ink/components/#form
Looks a lot like a raw HTML+CSS framework I made in 2009:
https://alganet.github.io/ghiaweb/ (it has some small glitches, browser widgets changed a lot since 2009).
Particularly the use of the label, fieldset and legend elements as native accessible solutions instead of instrumenting divs. Even the styling and the example resembles it a bit!
https://oat.ink/components/#grid
This is where it falls from grace IMHO. Grid classes are fundamentally non-semantic. I know they're popular and useful, but there must be a better (semantic) way of doing this. I haven't found it yet, but there must be.
For example, in Safari showModal for a dialog tag causes recalculating layout for EVERY element on a page, it’s up to 59x slower than chromium…. :(
But I love the idea
I like your presentation of the components, but i'm having trouble finding the essential distinctions
[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
edit: clarification, focus
edit: That is, the footer is not within a visible area of the sidebar.
Looks okay, but I don’t see why to use this over something like Marx if all you need is to not have bare browser default styling.
The upvotes on the submission look legit to me, as does the submission itself.
https://oat.ink/components/#form
Which actually makes sense: Oat's driving philosophy seems to be to use and enhance native controls as much as possible, and the date picker is already a native type on the input element.
there are other similar projects out, and i like them too.
