11–20 of 70 posts
It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
Squidex is MIT license and has reasonable pricing for their cloud offering, also has graphQL support and more feature rich.
The scary thing to me is if a service like this stops, I have an angry client and a lot of work. Headless CMS's are a delight to work with though.
I understand the benefits of all of these individual services, but I also miss the days of the only service I had to worry about when I handed off a client site was hosting.
Now it's often the headless CMS hosting (i.e. Contentful, GraphCMS), actual hosting (Netlify), CDN, Image CDN, Search (i.e. Algolia). So many places for things to break. So many separate charges.
I also love headless CMS's but much prefer self-hosted ones. Directus has been a favorite to experiment with so far.
Earlier quoted context omitted.
Hey! I'm one of the co-founders of GraphCMS. We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs. Most of our customers just want us to take care of the hosting.
Can you compare pros/cons to Contentful?
In the future, our focus will shift even more to content based BaaS as we will support end user authentication. We are also preparing a new suite of workflow tools that will make managing large datasets a breeze.
It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
It's really, really hard to build an open source (free) product that makes any money. GitLab works because it's a very complex product that a few really large companies are willing to spend hundreds of thousands of dollars on it. I can't imagine that being true of a CMS. That being said, different genres of software have "known" price points. For source control, it's expensive. For analytics, it's expensive. For blog…
It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
Earlier quoted context omitted.
See Directus https://getdirectus.com
Directus is always at the top of self-hosted CMS lists, but one of the reasons I avoid it and other PHP self-hosted headless CMS solutions is due to the difficulties(tech debt) of automating dev environments and CI/CD pipelines across different distros and OSes. I would have possibly given Directus a spin if it didn't have hard dependencies on the following PHP system extensions: curl, gd, finfo, pdo_mysql and mbstri…
It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
Hey! I'm one of the co-founders of GraphCMS. We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs. Most of our customers just want us to take care of the hosting.
The scary thing to me is if a service like this stops, I have an angry client and a lot of work. Headless CMS's are a delight to work with though.
One benefit of the nature of a headless CMS though, is that there can't really be a vendor lock-in on your content.