4 ms·
But can a web-based updater can still generate a static back-end?
by gwbas1c 9y ago
But can a web-based updater can still generate a static back-end?
- bigmanwalter 9y agoDepends what you mean by "static" at this point. I've created sites that were updated infrequently, and so I wrote a script to build out a static mirror of the site after updating. By exposing only the static mirror you get the best of both worlds. For a higher end setup, you can run a static caching layer on the HTTP server netting you the same performance benefits but without manually building the mirrored version.
- soft_dev_person 9y agoThere already exists some nice projects for this, like https://www.netlifycms.org/ https://www.netlifycms.org/
- icebraining 9y agoThere's also Movable Type, which has been around for 16 years now.
- bigmanwalter 9y agoThat's fine for content based sites, but often times the client wants to edit their homepage as well.
- wastedhours 9y agoWill be interesting to see when the next generation of "content APIs" hit - client updates a field in a backend somewhere and it rolls out to static sites, apps, bots etc... all over.
- deleted 9y ago[deleted]