Saving fish by writing code! Applications developer in fisheries, specializing in webapps and moving 'enterprise-y' legacy systems to modern agile systems - Email or tweet me if you want to talk!
JAMstack is a really useful term that comes close to what I'm imagining. My quibble is that I'd like to get away from editing so many templates for simple applications. Sometimes, I just want to make the app, rather than make the templates to make the app.
In my minimalist, non-JAMstack conception, I picture a utility that you feed a form to. It outputs a Dropwizard application. When you run the application, you may go to an admin interface that walks you through the configuration you need to do (credential setup, where is your database, what's the address). From there you can create the initial database structure and have an administrative view of the data you've collected and your api docs. It also would host the form and provide an api.
In my maximalist, possible SAAS conception, I picture a service you give your form to you. It asks you the configuration quests, then creates a storage bucket and a lambda, hosts the static file and gives you a useful admin interface. Explains how to integrate into the rest of your site.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this could be useful if it fits in just right. Would this be designed to sort of fit in as a JAMstack utility tool? Would want more details.
JAMstack is a really useful term that comes close to what I'm imagining. My quibble is that I'd like to get away from editing so many templates for simple applications. Sometimes, I just want to make the app, rather than make the templates to make the app.
In my minimalist, non-JAMstack conception, I picture a utility that you feed a form to. It outputs a Dropwizard application. When you run the application, you may go to an admin interface that walks you through the configuration you need to do (credential setup, where is your database, what's the address). From there you can create the initial database structure and have an administrative view of the data you've collected and your api docs. It also would host the form and provide an api.
In my maximalist, possible SAAS conception, I picture a service you give your form to you. It asks you the configuration quests, then creates a storage bucket and a lambda, hosts the static file and gives you a useful admin interface. Explains how to integrate into the rest of your site.