What Next?

Eight years—that’s how long it’s been since the last post on this blog. What happened?


I got bored and got the hell off social media and and wiped all my profiles clean and turned this blog private. I didn’t really feel like I wanted to tweet or blog anymore.

But now I’m bored of that too, so I’ve been shitposting on Twitter for a short while again recently and I figured I’d do the longer form of that out here once again. So, here we go.

What happens next is actually a bit interesting. To me, at least.

I was in the process of rebuilding my personal/portfolio website—as we developers do—and after a polyamorous period of affairs with Gatsby, Eleventy, Astro, Svelte and SolidJS, settled down once again with good ol’ Next.js.

I just wanted a simple static site with content pages, some interactive stuff and a simple blog. The obvious choice is MarkDown files in a posts folder, right? I know that’s what everyone’s into nowadays, but I’m not particularly excited about putting all my blog posts into my source code on GitHub. Call me old fashioned, but I like the content editing experience of a real CMS and I didn’t want to use the GitHub Codespaces editor as my CMS on the go. I didn’t want to use Sanity or Contentful either, because that stuff is overkill for a simple blog.

That’s when I remembered I used to have a WordPress blog, so why not use that? Next.js’s static site generation (SSG) feature anyway allows you to pull in content from a headless CMS and WordPress offers an API for this. However, I had only used the API on self-hosted blogs. The last time I used WordPress as a headless CMS  was in 2018 for a mobile app frontend and that was a self-hosted site. I didn’t want to set up another WordPress instance on Digital Ocean or something just this purpose. Again, overkill. Does WordPress.com offer an API too? It does! I don’t know why I never asked myself this question earlier!

I’ve set it up along with getStaticPaths and getStaticProps and also implemented Incremental Static Regeneration (ISR), so I don’t have to manually trigger site builds or even use On-demand Revalidation (ODR). I’ll just post things on WordPress and they’ll show up on my site whenever someone visits. I’ll set the revalidate time to a comfy 24 or 48 hours, since I’m certainly not going be as prolific with my posts as I used to be with my tweets.

That’s what’s Next!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close