I’m not sure how to abstract all things out. A big part of my love for Netlify and the JAMstack is that every page starts and works for everyone with just plain markup. Everything that requires JavaScript (and APIs) I see as an enhancement. So for very dynamic and nice-to-have content I can imagine loading that in asynchronously and thus not affecting the initial page markup. For something like our opening hours we could consider that. However components that are part of the core navigation such as the header, I want to work regardless of the capabilities of the client consuming our website. So I will always want to include that in the static page markup.
Before we started using Netlify we had our own CI and hosting of static generated files using an Nginx server. We would use Server Side Includes (SSI) to include things like headers to abstract them out of our static page markup (<!--# include file="header.html" -->
). I see a thread on SSI on Netlify from which I understand Netlify has no such mechanism. Is that correct, or any plans maybe? (Sorry if this gets off-topic, I could start a new thread).
Thanks for disabling form processing on our project. I’ll mark your original answer as solution.