Let’s say I created an app on Netlify that uses 11ty to render database content into static files on build time. Nice.
Let’s also say, that I want users to be able to manipulate that data.
When a user creates some new content and that content gets into the DB, a Netlify redirect renders that data into a page dynamically until the deploy comes along the next time and updates the page. – I got this far and it works like a charm.
Now, let’s say the user later comes back to his page and updates some data on it. It would be an hard NO, to let the user wait until a whole new build of the entire application has gone through until he can se his changes on the site right?
So: Is there a way to tell Netlify to invalidate (or delete) only a single html page in the active deployment until the next build comes along? …that way, the user would the be redirected to the dynamic (lambda-based) rendering of his page and be happy. Then, when the next build comes along, his page will be static (and up to date) again until he changes his data again.
Is there such a thing? Can I somehow invalidate specific pages?
…or do I need a completely different approach to user UPDATED (in contrast to created) content?