Recent submissions

Comment · 5 years ago
This is the way. Define a problem and then find a solution. Don’t look at Jamstack and then hunt for problems!
Comment · 5 years ago
Which site is this? Keen to resolve if one of my domains.

Tbh Wordpress nor Jamstack solve bad html.

Comment · 5 years ago
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.

Comment · 5 years ago
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.

Comment · 5 years ago
entirely agree with you. Problem is I didn’t need a CMS. I was using Wordpress as a design tool.
Comment · 5 years ago
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?

Comment · 5 years ago
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.

Comment · 5 years ago
Comment · 5 years ago
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.

Comment · 5 years ago
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).

Comment · 5 years ago
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.
Comment · 5 years ago
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.

Comment · 5 years ago
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.

Comment · 5 years ago
My own?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton