Lots of my previous employers had "data structures to forms" tech. It's very useful.
GolemUI looks like a nice open source version of this idea.
Thank you!
Show HN: GolemUI – Declarative Form Engine
41–50 of 73 posts
Re: Show HN: GolemUI – Declarative Form Engine
#42Lots of my previous employers had "data structures to forms" tech. It's very useful. GolemUI looks like a nice open source version of this idea. Thank you!
THANK YOU!
Being three devs here on a table reading comments and feeling nervous, is great to hear this kind of feedback, we really did pour our souls here.
Re: Show HN: GolemUI – Declarative Form Engine
#43How do you handle schema migrations? If someone has thousands of JSON form definitions stored in a database and the component API changes, is there a migration strategy or versioning system built in?
Re: Show HN: GolemUI – Declarative Form Engine
#44Why did your release jump from 0.17.0 (2026-06-08) to 1.0 in such a short time? If I use Tailwind, BEM or Boostrap, how hard it will be to customise? Flowbite have a few pre-made UI. Shoelace UI is based on Web Components, now that it got bigger: https://webawesome.com/docs/components/
I guess you are implying how mature we are? If so, I think you can see this on our github commit log: https://github.com/golemui/golemui/commits/main/?since=2025-... Note the date! 2025-09-01, that is the date of our first commit, 1962 commits later we published v1.0 So you can see this has been well thought
I'm saying the version from 0.17.0 -> 1.0.
While other projects, such as Astro Starlight for documentation and Hugo CMS, have not yet reached 1.0.
Re: Show HN: GolemUI – Declarative Form Engine
#45Earlier quoted context omitted.
I guess you are implying how mature we are? If so, I think you can see this on our github commit log: https://github.com/golemui/golemui/commits/main/?since=2025-... Note the date! 2025-09-01, that is the date of our first commit, 1962 commits later we published v1.0 So you can see this has been well thought
I'm saying the version from 0.17.0 -> 1.0. While other projects, such as Astro Starlight for documentation and Hugo CMS, have not yet reached 1.0. https://starlight.astro.build https://gohugo.io
We are trying to signal that our product is ready to be used, is matured, but is v.1.0 as in this being the initial release... I don't think you would get two companies fully agreeing on their versioning strategy though...
Re: Show HN: GolemUI – Declarative Form Engine
#46How is this a new paradigm? This idea for JSON -> form has existed for a decade, one example: https://github.com/eclipsesource/jsonforms
The basic idea of declarative forms goes back way further than that. I wrote a Perl library that generated a form from Oracle table metadata 30 years ago, and I very much doubt I was the first one to think of it.
I haven't looked at Golem specifically, but every other approach I've seen breaks down for complicated UIs. User-friendly validation and conditional forms require procedural logic. Invariably the declarative format (JSON in this case) ends up with up with a bunch of programming constructs.
Re: Show HN: GolemUI – Declarative Form Engine
#47How do you handle schema migrations? If someone has thousands of JSON form definitions stored in a database and the component API changes, is there a migration strategy or versioning system built in?
I don't think there is a simple answer to that, if moving from a big project to GolemUI or any other platform, the key would be to do it iteratively, first starting with a POC and then slowly intaking the rest of forms, if you were to consider doing a POC with GolemUi we will more than happy to help with this obviously :)
Re: Show HN: GolemUI – Declarative Form Engine
#48How is this a new paradigm? This idea for JSON -> form has existed for a decade, one example: https://github.com/eclipsesource/jsonforms
The basic idea of declarative forms goes back way further than that. I wrote a Perl library that generated a form from Oracle table metadata 30 years ago, and I very much doubt I was the first one to think of it. I haven't looked at Golem specifically, but every other approach I've seen breaks down for complicated UIs. User-friendly validation and conditional forms require procedural logic. Invariably the declarative…
Indeed, this is an old principle, we believe the key here is how we approach it, for instance, if you have a look at our DX layer (the gui.*) you will see how we bridge both worlds:
https://golemui.com/dx/form-definition/overview/
Have a look specially at the tags and selectors
Re: Show HN: GolemUI – Declarative Form Engine
#49[flagged]
We've banned this account. If you want to use a different (non-trollish) username, and commit to following the site guidelines (which you broke with this comment), we'd be happy to unban it.
Re: Show HN: GolemUI – Declarative Form Engine
#50This looks very much like many slopped up UIs I've seen over the past few years. Not saying the code is, but the design itself looks vibe coded?