[nihil75]

Headless-CMS makes this platform obsolete from the get go. The modern approach of separating responsibilities dictates that a CMS should not handle the rendering of pages, but rather provide a publishing interface and "content-as-a-Service" for whatever frontend/edge-device the site is presented on.

[dewey]

I'm pretty sure there are cases where people don't want to have the modern approach and run two services for it. Having a random CMS taking care of these tasks is good enough for a lot of use cases.

[alegauss]

Great! We are creating a set of Rest APIs and GraphQL to also use Shiohara CMS as Headless CMS