ridings

This is the way. Define a problem and then find a solution. Don’t look at Jamstack and then hunt for problems!

Which site is this? Keen to resolve if one of my domains.

Tbh Wordpress nor Jamstack solve bad html.

Honestly this thread is my favourite.

My blog isn’t Jam. It’s a ghost on T2.micro. This hit the FP and it didn’t like it.

Can’t help but think if it was Jam it wouldn’t of gone down. Then again I like the editor for ghost.

Either way, I’m not protective over Jamstack, this whole situation is ironic and funny.

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.

entirely agree with you. Problem is I didn’t need a CMS. I was using Wordpress as a design tool.

From the comments I’m learning the obvious. There isn’t one approach because there isn’t one problem.

This was a success because I really understood what I was solving for.

Each scenario will change and the solution will too.

TLDR of the article; what do you want?

I use VSCode locally. I can make some really small untested edits in github for typos and stuff.

Did think about putting a WYSIWYG editor in there but decided I didn't need one.

There is something funny about this but HN killed my blog. Added the Markdown content here: https://github.com/Ridingst/hillcroft-site

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.

Honestly - I like ghost and setup was pretty straight forward. The personal blog was as much a sandbox and learning environment as anything else.

I'd be tempted to do Jamstack for it in the future and remove the Ngninx overhead all together (even if just to get rid of the ssl certificate side).

Error on my part. Shared the link and realised I needed to patch ghost. Took the site down for 5 mins while that was happening.

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.

I don't think Jamstack will become the dominant way to build webapps. 95% of this site was static, brouchure-esque content.

I wouldn't try and build a live dashboard using real-time metrics or data intensive graphs using Jamstack.

My own?

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.

You probably can't and I guess that's ok. I didn't need those features for the project.

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!

Anyone smart enough to help me understand why UK would be exempt?