I was trying to avoid bringing it up but it seems it’s impossible. If I signed up with Contentful there’s actually a free tier that fits the workflow above and is completely hosted.
The workflow above fits with the Contentful API. I can fetch content that’s “mostly static” (ie: blog posts after authoring) and still use a proxy or access to the Contentful API to access items that I want to be more dynamic. Contentful lets you split your queries into primitive objects to make this even more useful.
If you review Strapi features…
This is how I’m using my current Ghost instances. You will see that it aligns completely with the Headless CMS Explained in 5 minutes link you provided.
if you were to host Ghost by yourself you wouldn’t be using a CDN
This is incorrect. The storage plugins in Ghost facilitate this. When I upload an image in Ghost it plops right in a GCP bucket that I can access through a subdomain like “myblog.ghost.tld” (non-public to users, hosted on ghost, obviously public on the internet) and simultaneously “myblog.tld” allowing the images to be rendered by both public URLs (in and outside of Ghost authoring, for example). Even without the custom storage adapter I can just push content from Ghost’s local storage.
Competitors even offer a media library - a requested feature of Ghost here on the forum. As a bonus with some of the headless CMS services I even get namespaces.
I would rather use Ghost. The lowest pricing tier for Ghost is $36 monthly. The challenge I’m running in to is justifying $36 for a CDN, custom domain, and custom certificate that will never ever be directly accessed by readers. It’s on Ghost’s pricing page.
On the pricing page there’s specifically a callout for “Use a custom SSL certificate” and that’s why a certificate was brought up. Why does the Ghost team keep insisting on explaining TLS? That’s not at all the point. And why do I get this condescending suggestion that I have no understanding of architecture? This is really easy stuff.