Honestly, yet another CMS that ties your UI to your CMS is not what we as an industry need.
I know it seems nice and it has a lot of nice features (features that have been in other CMSes before) .. but this is just an old school way of thinking.
Any enterprise, before anything else, should be looking at headless CMSes, primarily in my opinion. This is what I advise all of our enterprise clients. (we have no horse in the race)
The benefits of headless CMSes are multiplied by enterprises with very large and rich content needs, and generally, what these businesses need, is less coupling of things.
I'd rather look at something like strapi, which is open source, has a MVC architecture built on express, is headless by default, more than a single db option, has a graphql api etc.
Or if you want to go SAAS, use Prismic.io or Contentful
Decoupling the pieces that make up the editorial process brings modern practices to the table, for sure, but it also adds another level of management that the enterprise market as a whole just doesn't seem to enjoy. It's easier to sell them a solution that integrates everything into one marketable package.
Comments
Honestly, yet another CMS that ties your UI to your CMS is not what we as an industry need.
I know it seems nice and it has a lot of nice features (features that have been in other CMSes before) .. but this is just an old school way of thinking.
Any enterprise, before anything else, should be looking at headless CMSes, primarily in my opinion. This is what I advise all of our enterprise clients. (we have no horse in the race)
The benefits of headless CMSes are multiplied by enterprises with very large and rich content needs, and generally, what these businesses need, is less coupling of things.
I'd rather look at something like strapi, which is open source, has a MVC architecture built on express, is headless by default, more than a single db option, has a graphql api etc.
Or if you want to go SAAS, use Prismic.io or Contentful
Decoupling the pieces that make up the editorial process brings modern practices to the table, for sure, but it also adds another level of management that the enterprise market as a whole just doesn't seem to enjoy. It's easier to sell them a solution that integrates everything into one marketable package.
It looks like it can be headless if you want it to be. https://github.com/apostrophecms/apostrophe-headless
Confirmed, can run fully-headless or a mix of hybrid with mix-ins.
I would also check-out https://github.com/tinacms/tinacms which allows simple markdown editing on Gatsby and Next. It's as extendable as you'd like.