What problem does it solve?
Setting up the self-hosted Nuxt Studio editor involves coordinating module configuration, OAuth authentication, Git repository targeting, and SSR deployment, and misalignment between any of these pieces breaks login or publishing.
Core Features & Use Cases
- Module and repository configuration: Install nuxt-studio, set the editor route, and point it at a GitHub or GitLab repository with branch and monorepo rootDir support.
- Authentication setup: Configure GitHub, GitLab, or Google OAuth with the correct NUXT_STUDIO_AUTH_ environment variables and callback URLs.
- Live editing and publishing: Work with visual/MDC editors, schema-driven forms, drafts, media libraries, and the Git-based publish cycle on SSR deployments.
- Use Case: A team wants non-developers to edit Nuxt Content pages in production. Use this Skill to wire Studio to the content repository, configure GitHub OAuth, and verify one full publish cycle from draft to deployed commit.
Quick Start
Set up Nuxt Studio in my Nuxt Content project with GitHub OAuth and verify that publishing a draft commits to the main branch.