4 ms·
"Users can create a form" and "simple" are not two things I would put in the same sentence. What's happening in the forms? Where does the form go? How many user
by the_other 4y ago
"Users can create a form" and "simple" are not two things I would put in the same sentence. What's happening in the forms? Where does the form go? How many users? This immediately sounds "bigger than a web page" and suggests you need _some_ tooling.
Presumably, you will need a back-end and you could do the front-end in either browser-land or server-land. If you're a back-end or systems developer by background, do it in the back-end. Get a well featured back-end tool to do most of this for you. Django, Rails etc. If you want realtime UI updates (form construction, validation hints), think about a "hot HTML loader" paradigm such as Hotwire[0]. IIRC, some/all of Hotwire is built into Rails now.
CAVEAT: I've been too deep in js-land to know if Hotwire's any good. It's the one I'd look into first from having read around a little. Svelt second, but I suspect Svelt has got too much "build time" tooling for your size project & coding preferences.
[0]: https://hotwired.dev https://hotwired.dev
- mpeg 4y agoIt is simple, people have been processing forms with CGI-style tools for ages (php etc, even this website!). With modern web services the equivalent is to use zapier/pipedream or built in services like netlify forms. You can get a lot done with no /low code tools, heavy frameworks like django and rails are really not needed.
- notpushkin 4y agoI don't get your analogy here. How exactly is Zapier equivalent to CGI?
- mpeg 4y agoIf you want your static html to process a form, a few years ago the simplest approach was to add a php file to your site. Nowadays it is to create a zap webhook and point your form there. My point was that this is not and has never been a complex thing requiring a framework or a complex backend.
- notpushkin 4y agoMakes sense, thanks!