phlex VS shoelace-css

The community was a delight! I can't even count how many people I connected with, and it was just great to meet people whom I had previously only interacted with online. Also got to meet a lot of those people who significantly contribute to the Rails ecosystem. Everyone I said hi to was more than willing to spare time and nerd out and share experiences. I was also thrilled to connect with Philip, who shares my enthusiasm for Phlex. He provided me with some exciting ideas for creating an even more crazy yet cohesive form object with Phlex.

Why use ActiveAdmin or RailsAdmin: Brick is not nearly as configurable -- at least yet! With Brick you can drop in your own model / controller / view template and it will use it, but on its own you can not change theming / use it to do templating tricks / etc. Currently working hard to arrive upon a straightforward and logical approach so that all of this will be possible. Looking into Arbre (used by ActiveAdmin) and Phlex for inspiration.

Phlex is an incredibly refreshing gem created by Joel Drapper. It introduces a remarkable way to build views in pure Ruby, as exemplified below:

A few months ago I came across https://www.phlex.fun and thought it was a nifty little library that could be useful for creating components. Since then I've been playing around with it in Rails, using it more seriously, and finally took it to a point where I built a Rails application with 100% Phlex components and 0% Erb. The other crazy thing is I figured out how to inline the Phlex view components into a controller, so prototyping Rails apps feels vaguely familiar to prototyping one in Sinatra.

A colleague has been using Phlex and I’ve since tried it as well. For me having it all be straight ruby, in one file, has worked and just from my personal preference something I’ve enjoyed over view_components.

phlex

You might want to take a look at Phlex, which essentially has the same syntax: https://github.com/joeldrapper/phlex

HTMX gets all the hype right now, but there are other tools in the same vain, my favorite being Unpoly (https://unpoly.com). Together with Shoelace (https://shoelace.style) you get nice GUIs real fast, without the burden of complicated dependency management and build steps. Also, you don't have to write a lot of JS, just what is needed for small enhancements, as it was meant to be. Some might say the main drawback is the tight coupling to your backend. In my case, this is also the main benefit as it integrates perfectly with the backend framework (Django).

Hello HN,

I'm releasing Hyperdiv (https://hyperdiv.io), a framework for rapidly developing reactive browser UIs in Python, with immediate-mode syntax and using Shoelace (https://shoelace.style) as its built-in component system.

This short coding video will give you a good idea of what it is: https://www.youtube.com/watch?v=4XJKfxaqvGE

I wrote a brief article about the motivation and approach: https://hyperdiv.io/intro.html

Hyperdiv doesn't aim to compete with serious full-stack frameworks. The core aim was to make it easy and fast to prototype apps and build UI-based tools. I was originally motivated by internal tools at work -- feeling the need to quickly put together UI-based tools to share with both technical and non-technical coworkers, without having to stand up and maintain a full internal stack.

This is my first major open source release. I really appreciate your feedback and support. - Marius

For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.

Here's what this looks like - note that I'm using Shoelace components for styling purposes.

There are lots of open-source design systems built with Lit. Shoelace is a popular component set that you might check out: https://github.com/shoelace-style/shoelace There are many others...

Would it help if we listed more open source projects on our site?

Because of our focus on components and the fact that you really can use just about any libraries and scaffolding for apps, we don't really have an app starter kit, but it's something we've talked about.

I'm really excited about all this, and it makes me have some faith in the web again. I think that Lit is a step in the right direction especially the ability to do SSR / SSG and hydrate a web page. Hopefully 🤞 Shoelace can get SSR running, which is currently one hurdle, but I think it is achievable.