Prototyping with headless CMS

One easy way I sometimes validate software architectural solutions I am working on is through ๐—ฝ๐—ฟ๐—ผ๐˜๐—ผ๐˜๐˜†๐—ฝ๐—ถ๐—ป๐—ด.

According to wikipedia, a prototype is an early sample, model, or release of a product built to test a concept or process. In my case it validates that the solution fits, and must do it fast.

To make thinks easier I leverage as much as I can on existing tools, libraries or platforms and only build what is needed to validate the solution or proof a concept.

To substitute backend services doing simple CRUD operations I use ๐—ต๐—ฒ๐—ฎ๐—ฑ๐—น๐—ฒ๐˜€๐˜€ ๐—ฐ๐—ผ๐—ป๐˜๐—ฒ๐—ป๐˜ ๐—บ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐—บ๐—ฒ๐—ป๐˜ ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ๐˜€. What a headless CMS does is making content available through an API, allowing me to use it as a content repository.

Headless CMS come in many different forms and implementations. Some have OAuth2 support, some have GraphQL support, some support certain databases.

Of course, headless content management systems are not just useful for prototyping, some are mature products that can successfully be used in production systems.

To decide upon which headless CMS to use based on your requirements, the website is very useful.