Ok, I have to find a suitable CMS what will serve as backbone for my newly developed PWA application and I have no idea which one to choose. Because of that I have decided to list my thought and maybe even get some suggestions from others. This post supposed to be as short as they can, so I will switch directly to the point.
This is not an blog post with solution, it is more about the questions and my understanding what I expect from CMS. Also I hope it will be a series of blogposts where I will rise more question and at the end, at lease I hope those questions will lead to some answers and final solutions.
Recently I and my team have developed mobile PWA application. Project is almost done, some final design related updates will be added and the project will transition in maintenance stage. The current customer has his own CMS and a lot of content. Now I have to move this product forward and need to find some CMS for it. Also the same CMS should be suitable for new upcoming applications and customers.
So this is where new theme of thoughts started to spin in my head. And the main challenge is. I need some CMS to be used for new customers, it has to be flexible, performant and easy to maintain and extend.
I had some ideas already, but has to look at the current situation and to figure out what CMS could be used as a solution for my future customers.
After thinking about present situation and doing some research I was not able to come to any suitable solution. And this is a blog post where I have decided to gather and document some requirements specific for me.
Here is a list of questions and thoughts for current day, this is a kind of brainstorming out coming and should be treated as such.
Currently I was not been able to find anything what fits above list expectations. I becoming kind of sad and coming to the realisations that something new should be done and probably I will start reviewing source code architecture and API of current, popular open source CMS.
As more CMS will be reviewed and evaluated I will add new following posts.
This is not an blog post with solution, it is more about the questions and my understanding what I expect from CMS. Also I hope it will be a series of blogposts where I will rise more question and at the end, at lease I hope those questions will lead to some answers and final solutions.
Recently I and my team have developed mobile PWA application. Project is almost done, some final design related updates will be added and the project will transition in maintenance stage. The current customer has his own CMS and a lot of content. Now I have to move this product forward and need to find some CMS for it. Also the same CMS should be suitable for new upcoming applications and customers.
So this is where new theme of thoughts started to spin in my head. And the main challenge is. I need some CMS to be used for new customers, it has to be flexible, performant and easy to maintain and extend.
I had some ideas already, but has to look at the current situation and to figure out what CMS could be used as a solution for my future customers.
After thinking about present situation and doing some research I was not able to come to any suitable solution. And this is a blog post where I have decided to gather and document some requirements specific for me.
Here is a list of questions and thoughts for current day, this is a kind of brainstorming out coming and should be treated as such.
- CMS should be API based or Headless CMS (alternative naming).
- Should be easy to integrate with other services and micro-services.
- All the parts of CMS preferred to be swappable, I would like to have a set of Abstraction API layers where I could replace different parts of the system.
- Should be an open source.
- Should have nice and easy and clear way for creating new content types.
- Should have nice and easy to use Content Editor.
- Should be configurable to work with different data base and data storage technologies.
- Provide some workflow and content release and management processes. Should be customisable.
- Should be stable and performant.
- Based on my experience Preferably should be Golang, NodeJS or Java based. Other options are possible, but I will be very cautious.
- List of expectations will definitely grow as time goes and the will be reviewed and updated.
Currently I was not been able to find anything what fits above list expectations. I becoming kind of sad and coming to the realisations that something new should be done and probably I will start reviewing source code architecture and API of current, popular open source CMS.
As more CMS will be reviewed and evaluated I will add new following posts.
Comments
Post a Comment