Feature: From Contentlayer to Content Collections

[Codehagen]

Type of feature

💡 Feature

Current behavior

We are currently using Contentlayer, a content SDK that transforms Markdown & MDX content into type-safe JSON data for React applications.

Suggested solution

Remove Contentlayer and move into Content Collections. Content Collections is a Contentlayer-inspired content framework created by Sebastian Sdorra. It addresses limitations found in Contentlayer, such as the inability to define an email or URL type for a given field.

Additional context

Contentlayer has been effectively unmaintained since their main sponsor, Stackbit, was acquired by Netlify. Additionally, there are issues like Next.js App Router incompatibility. Here is a link to see how we need to do it:
Content Collections Blog Post

Here is their GitHub repository:
Content Collections GitHub

[linear]

BAD-48 Feature: xxx

[akyndev]

.take

[github-actions]

Thanks for taking this issue! Let us know if you have any questions!

[akyndev]

What's the value of raw parsed in the body, it doesn't seems to be on content-collections body

[Codehagen]

Big Rework on Badget - Autoclose all PRs