Live data from Hacker News

Show HN: Rails UI

railsui.com

41–50 of 116 posts

Re: Show HN: Rails UI

#43
Good to see work in non-AI world and for Rails!

I would make it clear in the landing page that the components are for demonstration purposes by adding a title like "For example" before them.

The above the fold looks a bit packed right now. I would leave the login box out until user presses top right as it's for retentive users only.

Re: Show HN: Rails UI

#44
post #43

Good to see work in non-AI world and for Rails! I would make it clear in the landing page that the components are for demonstration purposes by adding a title like "For example" before them. The above the fold looks a bit packed right now. I would leave the login box out until user presses top right as it's for retentive users only.

Agreed - particularly because there is an example of a login box and the screenshot of that is far more prominent than the rest of the design.

I don't think the demo should overpower the landing page.

And then it goes straight into themes. If I'm a Rails developer I'm not looking at theming, I'm looking for a conventional UI system that fits into Rails - stimulus, Hotwire, all that.

As far as I know, this site so far is just a bunch of specialised scaffolds for certain use-cases, but Rails itself has been capable of that the entire time.

Re: Show HN: Rails UI

#45
post #43

Good to see work in non-AI world and for Rails! I would make it clear in the landing page that the components are for demonstration purposes by adding a title like "For example" before them. The above the fold looks a bit packed right now. I would leave the login box out until user presses top right as it's for retentive users only.

Thanks for chiming in!

The login box is maybe confusing or maybe I'm misunderstanding you, it's actually UI for a login box, not actually where you login. I agree this area could be tightened up.

Re: Show HN: Rails UI

#46
post #44
post #43

Good to see work in non-AI world and for Rails! I would make it clear in the landing page that the components are for demonstration purposes by adding a title like "For example" before them. The above the fold looks a bit packed right now. I would leave the login box out until user presses top right as it's for retentive users only.

Agreed - particularly because there is an example of a login box and the screenshot of that is far more prominent than the rest of the design. I don't think the demo should overpower the landing page. And then it goes straight into themes. If I'm a Rails developer I'm not looking at theming, I'm looking for a conventional UI system that fits into Rails - stimulus, Hotwire, all that. As far as I know, this site so far…

Good feedback! This is a common misconception about themes. Rails UI is more of a hybrid as it offers UI components plus optional pages that build out a theme using those components.

You can either take the pages and tweak them for your own use case, or just use the UI components and skip the theme entirely. If you get a chance, try the free Ruby gem to see what I mean.

Re: Show HN: Rails UI

#49
This definitely does fill a gap that Rails has. I love using it but man I can't make a nice looking front end to save my life. We've used Tailwind UI a ton but thats kind of a foot gun because you end up slightly tweaking classes all over the place if you're not disciplined.

Re: Show HN: Rails UI

#50
It looks good, but I'll be honest, it's hard for me to consider $299/$799 if I can buy a beautiful theme off of somewhere like ThemeForest for $20 or $30 and toss it into an LLM to get the files parsed into components and templates.
Post reply on HN