Determining the Tech Stack: Backend
August 16, 2022
I will use the Headless Content Management System (CMS). I decided to use Headless CMS, and what I chose was Strapi.
This blog is part of Building my personal portfolio with Vue.js, Strapi and MongoDB series
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?
- Open-source CMS
- NodeJs
- Strapi's Documentation, Plugins and API
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.