Adityacprtm

Aditya Pratama

DevO
  • EmailEmail
  • Location Jakarta, ID
Return to Blog

Determining the Tech Stack: Backend

August 16, 2022 · 1 min read

I will use the Headless Content Management System (CMS). I decided to use Headless CMS, and what I chose was Strapi.

Adityacprtm
Part of seriesBuilding my personal portfolio with Vue.js, Strapi and MongoDB

For the backend, of course I will use the Headless Content Management System (CMS). Prior to this, I already had a CMS that I built using Laravel. But the CMS is a traditional CMS like wordpress, joomla and others where the backend and frontend are inseparable from each other. This means that the CMS can only be used or consumed for the same frontend, in this case Laravel and Blade.

Of course, the CMS can be changed as an API provider, but there will be a lot of configuration and I don’t want that. So, I decided to use Headless CMS, and what I chose was Strapi. Why Strapi?

  1. Open-source CMS
  2. NodeJs
  3. Strapi’s Documentation, Plugins and API

Strapi.io

In a way, even no-coders can use and run Strapi. Minimal configuration and easy to use, especially for building REST APIs with many features, such as image optimization.

Visit the documentation from Strapi for more details.

Explored Topics
Comments
← PreviousStrapi Setup: Schema, Plugins dan DeployNext →Determining the Tech Stack: Front End
© 2026 Aditya Chamim Pratama