3 ms·
> Imagine you're going to build a new SaaS app. Would you think of building it on a headless CMS? I'm guessing this mostly makes sense for a SaaS that's mostly
by mwcampbell 4y ago
> Imagine you're going to build a new SaaS app. Would you think of building it on a headless CMS?
I'm guessing this mostly makes sense for a SaaS that's mostly about serving content to users. I wonder how common that kind of SaaS is, as opposed to a SaaS where the core functionality wouldn't be served well by a CMS, and the administrative tedium that one wants to alleviate mostly has to do with account management, payment processing, enabling or disabling service based on billing status, etc.
- jobsdone 4y agoThe point here is that it isn't just a tool for content. The way I see things, there is no useful distinction between content and any other kind of data. Payload makes it trivial to set up custom data structures and manage it. The tedium of development in my experience is building CRUD—whether it is for a SaaS app or anything else. When you're rolling a project using a framework you've got to set up a database, write the API logic and build an admin UI to manage that data. It is complicated and time consuming work even with a great framework. To be able to skip all that is a massive advantage. I personally would not build a SaaS app on Wordpress and ACF, but I would use Payload to build just about any custom business app.