Nuxt setup guides

42flows publishes to Nuxt by writing a markdown file into your content/ directory and committing it to your repo. From there, your own CI/CD takes over. These guides cover the decisions you need to make once.

How Nuxt fits

Nuxt Content is one of the main 42flows website publishing paths. If you want the side-by-side view across WordPress, Shopify, Nuxt, GitHub, and webhook delivery, read Website content integrations and GitHub and Nuxt Content integration.

For the feature-level overview, see Nuxt Content publishing with 42flows.

Start here

• Connect your Nuxt site via the GitHub App — the fastest way to wire up a Nuxt Content site. We commit the four files needed; you don't write any code.
• Pick the right branch — and why "publish = live" matters — the single most important config choice for every Nuxt customer.

Coming soon

• Cache invalidation after a publish (ISR, Cloudflare, service workers)
• Draft vs published workflows with Nuxt Content
• Rendering 42flows content inside a custom layout

Don't see your issue? Reach out at [email protected] — every real customer problem becomes a new guide here.