I’ve been looking for a suitable blog CMS for sometime now to write up about my endeavours and content write-ups regarding any interesting things I stumble upon during my path as a programmer and an aspiring photographer. Medium, WordPress and many others immediately came to mind as options however they were quickly rejected due to several criteria I require.

  1. The ability to self-host the content on my own domain and host provider for privacy reasons. (Huge plus if it’s open-source!)
  2. To seamlessly perform CRUD operations on my posts and content whilst pushing it to my website in realtime.
  3. Avoid any server rendering (completely) if possible to allow for the next criteria.
  4. Able to be hosted on Netlify or GitHub Pages to save resources and cost for my other Web Applications.
  5. Security-wise it has to be secure and not too strict.

With these in mind, Medium was out of the picture due to me not being able to host it on my own domain. There were also additional issues regarding Medium such as their ability to wipe out my entire account and its contents in one go which was a huge issue for me.

Next came options such as Ghost and WordPress. WordPress and Ghost were considerable options and I’ve tried to work with them but the huge hassle to setup and maintain drew me away from using it as my permanent publishing solution. Hence, I continued my search for months until now.

Introducing the JAMStack

The JAMStack is a web development architecture which features 3 components: JavaScript, reusable APIs, and finally the Markup. This approach allows the developer to not require the services of any host or servers, leveraging all of the available frontend on an CDN and utilise the API component for any “backend” stuff.

By setting up my blog this way, I would’ve fulfilled all 5 of my criteria with minimal setup and maintenance (more on this later). The blog is on my domain, it is updated in realtime, there is practically 0 server rendering since it’s on a Netlify and is very secure.

Maybe JavaScript isn’t that bad after all?

In my later posts, I will explain the technological architecture of my blog as well as a simple way to set it up. Thanks for reading my very first post!