Move all content to a CMS (Sanity.io)

[leerob]

Since many people fork this repository, I'd like to prevent them from including all of my blog posts and personal information. This PR moves everything from my data/* folder to Sanity, which gives me a number of benefits:

• Faster git clone times due to less files and images
• Easier forking for folks looking to use this repo as a template
• Ability to update content without redeploying

This is using the new v3 of Sanity: https://www.sanity.io/blog/sanity-studio-v3-developer-preview

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
leerob	✅ Ready (Inspect)	Visit Preview	Jun 19, 2022 at 11:53PM (UTC)

[leerob]

📝 Changed routes:

/blog	/blog/[slug]
(view full size)	(view full size)

/feed.xml	/sitemap.xml
(view full size)	(view full size)

/snippets/[slug]	/snippets
(view full size)	(view full size)

And 4 other routes:

• /api/exit-preview
• /api/preview
• /api/revalidate
• /uses

Commit 6c021e5 (https://leerob-cg4j1l9o0-leerob1.vercel.app).

[leerob]

TODO

• Switch back to pnpm once Dev Preview Fails to Run in PNPM sanity-io/sanity#3336 is resolved.
• Decide if I want to migrate the rest of the images included in public to sanity (images inlined in blog posts)

[leerob]

Think I'm gonna fix Preview Mode in a follow-up PR. Worth merging now!

[nvh95]

@leerob I think moving content to a CMS blocks people from directly proposing changes to your posts by sending a PR. I guess they have to submit a new issue instead of sending a PR (or worse, don't even propose changes).

If the goal is to prevent people from including blog posts we can consider git submodule (or similar solution), where you can put all your data in a separate repository. People can still submit PR (typo/ translations...) to your posts as well. (The idea is to separate code and content to 2 different repositories)

These are just my naive thoughts when reading your PR. I know there are trade-offs when deciding where to put content data (CMS/ mdx).

[leerob]

There's more benefits that just that, namely that I can update content without redeploying 😄

https://on-demand-isr.vercel.app/

[trm217]

@leerob Why did you disable the usage of preact in production?

[leerob]

There's currently a bug it seems where the meta tags in the head like title and description weren't working.

[Music47ell]

There's currently a bug it seems where the meta tags in the head like title and description weren't working.

I've been struggling with this issue for the past week. I undid all the changes I made, tried different versions of packages I'm using. Nothing worked.

Just now, I decided to get rid of preact because I noticed you're not using it and the meta tags in my site started to work again.

Little bit of searching in this repository, and I just stumbled upon this 🤦‍♂️😂