This is a super critical point.
I am a member and ran the site for 2 years prior to this change. I was the only person that logged in.
Honestly this technical solution isn’t for every scenario but I felt confident that nobody would be updating the site in WYSIWYG. Comes down to what you need. There are many tools for many jobs.
Ye I think this could get messy at a point.
This project ended up with 2 or 3 API endpoints which I pushed up as serverless to give me some centralisation.
Not sure how happy I'd be if I needed to stitch 50+ API services together but not every project has the same requirements and we shouldn't assume the same solution.
So there was a part of the story I haven't told.
The wordpress site was painfully slow to load and while I like the look of the theme it was costly from performance perspective.
I did try to render the wordpress site out to html but I just didn't find it plain sailing and after a couple of hours research/testing look for a new direction.
This wasn't so much the technical stability problem; time will be the real test here. With Svelte I was able to very quickly scan the repo and pickup where I left of, even with long gaps between work.
I don't disagree. There's lots of options for the content part. I guess the thing I was trying to point out here was that I didn't need a CMS. The content is static, the site is basically a brochure. I was happy just writing static HTML.
There is a certain irony on this. My blog site uses ghost not Jamstack. I was using an old version and it had a pretty bad exploit bug related to magic links.
I took the site down to patch and then put it back online...If I'd only used SSG for it too.
I should of moved my blog over to Jamstack.
I put this link out and then realised there was a magic link exploit in the ghost version I was using. I took it down to make some emergency changes...DOH!