81–90 of 295 posts
I use these because I know them and I don't need to look for code or docs. And I feel the the tooling doesn't get in my way.
I feel that a UI components library is better suited for how I think, than a drag and drop config tool.
Passing props feels simpler than digging into menus to link that JSON to that calendar.
If you need any kind of interactivity on the frontend, but are more comfortable with the backend, I would suggest looking at Phoenix LiveView [0] or a similar server-rendered HTML technology for your language of your choice [1]. In short, these solutions take JavaScript out of the mix entirely and basically let you deal with a single logical "app", rather than a separate frontend & backend. [0] https://github.com/pho…
Seconding this. I've been using LiveView in production for ~18 months now, on a couple of projects. Hugely simplifies the overall stack. Combine with TailwindCSS, TailwindUI.com, and you have some very powerful tooling at a low development cost.
I probably need to focus more on 'vanilla' back- and frontend stuff, but man has it been fun so far! Definitely made me enjoy my work more.
If you need any kind of interactivity on the frontend, but are more comfortable with the backend, I would suggest looking at Phoenix LiveView [0] or a similar server-rendered HTML technology for your language of your choice [1]. In short, these solutions take JavaScript out of the mix entirely and basically let you deal with a single logical "app", rather than a separate frontend & backend. [0] https://github.com/pho…
Other tools (except for Tachyons, these are maybe out of scope for a home lab):
- Tachyons [0] is a small (16K-ish) utility class framework.
- DaisyUI [1] is a free and open source component lib for Tailwind.
- WindiCSS [2] is built on Tailwind with some additional features.
- UnoCSS [3], an interesting on-demand atomic CSS engine that supports Tailwind CSS, WindiCSS, Bootstrap, and Tachyons.
[0]: https://tachyons.io/
[1]: https://daisyui.com/
For those recommending Tailwind, it's huge if you're using it from the CDN (318K uncompressed). Other tools (except for Tachyons, these are maybe out of scope for a home lab): - Tachyons [0] is a small (16K-ish) utility class framework. - DaisyUI [1] is a free and open source component lib for Tailwind. - WindiCSS [2] is built on Tailwind with some additional features. - UnoCSS [3], an interesting on-demand atomic CS…
I wondered if anyone’s working on the following:
Tailwind.js running on a cloudflare worker (so it’s a “CDN”) and calculates the postcss on first request and then caches it.
Wouldn’t that be the best of both worlds?
It achieves straightforward abstractions and great speed by not having a virtual DOM.
The syntax is also very pleasant.
Preact [0] + htm [1] Why? Preact is small, fast, and reasonably easy to use. But the main selling point for me was that, together with htm, I don't need any build system a la webpack. No node_modules folder. I just have to load one script (preact + htm bundled), define my components in plain javascript files and import them. Bliss for me. [0] https://preactjs.com/ [1] https://github.com/developit/htm Edit: Just read…
But for proper frontend projects, I would use typescript, and therefore a build pipeline.
Pick a "classless" CSS library from a site like CSSBed[1]. These are kind of like Bootstrap, except you don't need to write any CSS or apply any CSS classes in your HTML for them to work. No tooling necessary; just include a tag in your HTML document. If you'd like to try something similar to this "Tailwind" hotness everyone keeps talking about, try Basscss[2]. Again, no tooling, just need a tag.
Once you start needing to add interactivity to your site, htmx[3] is nice and decently simple. If you really want something React-like, Mithril.js[4] is very similar but much simpler.