There are a couple of free(with free tier) databases available in Vercel, try installing Neon storage in Vercel for your project.
vercel.com/marketplace/...

Content module detects Vercel environment and will use connected database.

If issue persists, gather/share logs and we debug together.

We are working on linters, formatters and soon we will publish more details about standard MDC structure

For nesting you don't need to indent or add extra colons. I agree that IDEs default markdown highlighter does not do great with MDC files. We are thinking of a plugin for JetBrains editors

There isn't any plan to replace the validation library or make it configurable, unless we see some necessity in it.

The module uses Zod to define schema, tables definitions, type generation and validations. These are outside of built bundle.

Indeed, it is possible to support different markdown parsers (like markdown-it, which is used by VitePress) in order to import content from VitePress or MDX.

There is also a good chance of finding some remark/rehype plugins that make it easier to support others.

Here is the source in the main repo: github.com/nuxt/content...

It is here: github.com/nuxt/content...

It is a separate document for each language, even a separate collection for each language

Most issues with Nuxt Content and Nuxt i18n are related to handling content routes and querying specific locales.
With Content v3 and its new Collections feature, both modules now work smoothly together.

The release date is yet to be decided, the date and other information about the new version will be announced in the repo. You can try the public alpha. checkout content3.nuxt.dev
All templates will receive an update