Sébastien Chopin

We are planning to support specifying a layout in the page, but actually there is a limitation with Nuxt 2 for assigning a theme dynamically, see my comment on https://github.com/nuxt/nuxt.js/issues/3510#issuecomment-736757419...

This will be possible only by using middleware for Content V2, the showcase will be visible once we open source Docus.

@danielroe do you mind updating it to the correct branch?

Hi @ElnuDev In order to use Vue components in the Markdown, we need the AST and that's what `remark` provides.

Re-opening for the nuxt content v2 that will be much simplier with different transformers supported. Cc @pi0

Beautiful work @danielroe ❤️ Shall we document more to use `app.config.ts` for such configurations from now on?

Could we take this opportunity to also give the possibility to set those values to `false` to disable keepalive, page & layout transitions?

Investigating at this issue, I found it reproductible when saving the plugin **and** having the http://localhost:3000 running with the WS to vite running. The error happens right after the `full-reload`...

Alright, made a reproduction without `@nuxt/content` v2: https://github.com/Atinux/nuxt-maybe-value-repro You will need to save faster and more times the `~/plugins/foo.ts` because I did not add any parsing logic in it, but...

Let's see once #3956 is merged first 😊