Blog post content shouldn't be in source control (headless CMS?)

[dbarnett]

Blog post content shouldn't be in source control (headless CMS?)

[dbarnett]

Probably want headless CMS and something like MDX.

Relevant links:

• https://watershed.com/inside/evolving-mdx-publishing-with-a-headless-cms
• https://omkr.vercel.app/blog/how-to-setup-a-dev-blog

[dbarnett]

Looked through the Watershed article and some sanity.io learning resources. The headless CMS paradigm looks neat. OTOH...

• I'm not completely sold on MDX vs. just MD for basic blog content
• Still not sure how translations would fit into that paradigm yet
• I suspect a bunch of downstream CDN/caching questions will become urgent once I make the leap from local md files to externally-stored content

Worth noting, https://github.com/hashicorp/next-mdx-remote says in their README:

But seriously, if you are trying to build a blog for personal or small business use, consider just using normal html and css.

but I might still opt to overengineer this in some ways if for no other reason than learning value.

[dbarnett]

Also assuming I do use Sanity, I'm hoping instead of deploying an instance of Sanity Studio somewhere I can just spin up a local Studio on-demand to manage CMS data, with probably some config/schema files lumped into this repo but not "embedding" Studio into the actual Next.js FE.