I would like to create a JAMstack app where users could log in/sign up so I would need authentication/dynamic pages. Those users will then have kinda like their admin/dashboard page where they can upload/read some information. Imagine it like when u create an account on Airbnb/Booking and then you upload info about your apartments. The other functionality would be to do a standard search via filters, just like you do on early mentioned apps and based on your search queries you get the appropriate results.
So, is the JAMstack with a hydration good fit or I should go with the standard SPA approach here? I guess it's since this is not a fully dynamic app and its contents will not be changing frequently, plus, I would like to use benefits of the JAMstack architecture.
If u agree with me and would go with the JAMstack what stack/workflow u recommend?
I'm going to host a webinar on ‘JAMStack: The What, Why, and How’ with Nimit Bhargava!
Saturday, 27th June || 4 to 5 PM IST
Please register on the link below to attend the Webinar and to get details about
Hi JAMstack community, I'm new here and I would like to share with you an announcement of Cloud 66 Prepress - a tool that helps you build and deploy Jamstack sites on your own cloud.
We welcome and appreciate any feedback. More info here: https://blog.cloud66.com/announcing-cloud-66-prepress