oinam-jekyll VS headlessui

As we are on HN, I'm going to assume that you are comfortable using Github and can follow instructions.

Write it on Github and publish on your domain. Github has an option for you to fire up a web-editor (VSCode) right there in the browser with the keyboard `.` (<- that is a period). So, you can write right then and there (I do it quite often these days).

When publishing, choose a Jekyll theme of your choice from Github Pages[1]. Your focus now are just enough plain text (Markdown).

If you want to bring it to your desktop/device, just checkout the repo and write. These days, my choice is to just write in Obsidian and don't even try to run Jekyll.

What do you get out of this? The simplicity of focusing on your writing with almost Plain Text while Github takes care of your theme, hosting, SSL, and custom domain[2].

Of course, you will need to book a domain and own it. I like Cloudflare[3] that takes care of pretty much everything you want to do with a domain for free. If you so wish, you can even let Cloudflare do the page building[4] and hosting while you keep Github for the source.

Plug: I build a super simple Jekyll theme[5] just so I can do this. I wrote an article about it on my website[6].

1. https://pages.github.com

2. https://docs.github.com/en/pages/configuring-a-custom-domain...

3. https://www.cloudflare.com

4. https://pages.cloudflare.com

5. https://oinam.github.io/oinam-jekyll/

6. https://brajeshwar.com/2021/brajeshwar.com-2021/

Simple.css is a well done classless 'framework'. I stumbled on it a while back and started using it and thought this can be my go-to styles for tit-bits of websites that I do for landing pages, family websites etc. However, this is pretty opinionated (including some animations) and I had to abandon it. But I remained inspired by its simplicity and forked my own[1] broke it down. I broke it down to the most basic, but then can be built on top of it -- progressively get a website "designed" far enough but not further.

If you are into these simple classes, check out Drop-in Minimal CSS[2] and choose the one that fits your need.

Simple.css is from an interesting guy, Kev Quirk[3], whose 512kb[4] website was on Hackernews a while back (don't recollect if it was a story or a comment). Hi Kev, if you are around.

If you are spinning up a simple website with classless styles, perhaps it is a good idea to add a print styles and I like Gutenberg[5] for that.

1. https://oinam.github.io/oinam-jekyll/

2. https://dohliam.github.io/dropin-minimal-css/

3. https://kevq.uk/about/

4. https://512kb.club

5. https://github.com/BafS/Gutenberg

Ah! This is brilliant. There are quite a few comments here about pitching this against other CSS frameworks or the actual use of this.

This is not a stand-alone framework or anything of that start. Treat as one of your scaffold components for your styling framework. Tailwind does this with their tailwind.config.js and is more of raw CSS design tokens. I just wish their commercial TailWindUI[1] make it easy to make use of it the better way.

I wish I saw Pollen a few months ago. I wanted to do an effortless design for my personal website and stick to as plain vanilla CSS as possible. The best way was to rely on CSS-Variables. I did do it from scratch[2]. It works though it is pretty hacky, and I'm not too concerned. Right now, I can swap few values and have an entirely different color scheme - light/dark version of my own, Nord Theme[3], and I will keep adding me whenever I get bored. I can even tweak the rhythms and spacing to my liking with just the variable. You should check out the demo[4] or look at the source[5] (wip).

For those who find this interesting, you should check out another interesting one I discovered a few months back -- css-media-vars[6].

1. https://tailwindui.com

2. https://github.com/oinam/oinam-jekyll/blob/main/_includes/cs...

3. https://www.nordtheme.com

4. https://oinam.github.io/oinam-jekyll/

5. https://github.com/oinam/oinam-jekyll

6. https://github.com/propjockey/css-media-vars

Catalyst is a comprehensive, fully componentized UI kit for modern React projects, built on the next generation of Headless UI. With Catalyst, you can create a custom set of components to use and reuse in your projects.

And that is why I was looking for a UI library that would deliver these things for a long time and today I am happy to announce that I have found it! It is Headless UI by the Tailwind Team.

Headless UI provides a suite of unstyled, fully accessible UI components perfect for developers who want full control over their interface design. It's a developer's canvas, offering the foundational parts needed to build a user interface without dictating the aesthetics, making it ideal for those who love to integrate with Tailwind CSS. With https://headlessui.com/, you can ensure that your applications are inclusive and easy to use for everyone, while also maintaining the freedom to craft a unique look and feel that aligns with your brand or style guidelines.

GitHub stars: 22.5k GitHub link: https://github.com/tailwindlabs/headlessui Documentation: https://headlessui.com/

Website: Headless UI

Few months ago, I discovered project called Headless UI and I instantly liked the idea.

In addition to Tailwind CSS, Tailwind Labs also created Headless UI, a collection of components that work well with Tailwind CSS.

Tailwind - Headless UI

Thanks for sharing! I love projects that reimagine entire ecosystems: there's a lot of value in imagining what could be if we didn't worry about what is.

Some feedback: your comparison of the various ListBox implementations[0] feels disingenuous. I know Vue best, so I looked at that implementation in detail, and it's got a lot going on that you don't attempt to replicate in your version. A few key features that are missing:

* Search—in the HeadlessUI version there are several hundred lines dedicated to making typing work for jumping to specific list items.

* Multiselect—HeadlessUI supports multiple selections, yours does not appear to. Again, this occupies a lot of lines.

* Focus management—HeadlessUI has a lot of code dedicated to smoothing out the focus management. In my testing, your implementation has pretty buggy support for using tab to navigate.

* The HeadlessUI version dedicates a lot of lines to types, where your Nue implementation is dynamically typed. This may be a feature for you, but in my mind those type declarations are doing important work.

* In general, the HeadlessUI implementation tries to be flexible for many use cases [2], while yours only needs to support the one demo list.

You also include this render.ts file [1] from HeadlessUI, which is more part of a bespoke sub-framework used by HeadlessUI than it is a necessary part of any old Vue ListBox implementation. If you're going to count that against Vue, then there are parts of Nue JS that should be included as well.

These kinds of comparisons are most persuasive if you can write all the implementations from the ground up, using idiomatic patterns for each framework and identical feature sets for each implementation. When you do that, it's easy to compare and contrast the frameworks. As it is, it's like comparing a house to a garden shed: yes, you've used fewer lines of code, but it's not obvious to me that that's a feature of Nue and not just a byproduct of a less ambitious component.

[0] https://nuejs.org/compare/component.html

[1] https://github.com/tailwindlabs/headlessui/blob/%40headlessu...

[2] https://headlessui.com/vue/listbox#component-apihttps://head...