Configure and operate the self-hosted Nuxt Studio editor for Nuxt Content. Use when working with nuxt-studio installation, editor customization, OAuth or custom authentication, media, drafts, Git publishing, or production deployment.
Nuxt Studio owns content editing and publishing. Nuxt Content owns collections, queries, parsing, and rendering.
nuxt-studio and @nuxt/content versions, deployment mode, repository provider, and authentication provider. Setup is understood when the editor route, Git target, and login callback all point at the same deployment.nuxt-content boundary.| Task | Open |
|---|---|
| Install, repository settings, OAuth/custom auth, editor filters, or environment variables | Configuration |
| Visual/MDC editing, schema forms, drafts, media, or AI assistance | Live editing |
| SSR deployment, Git publishing, branch strategy, conflicts, or monorepos | Deployment |
| Collections, validators, queries, hooks, or rendering | nuxt-content skill |
npx nuxt module add nuxt-studioexport default defineNuxtConfig({
modules: ['@nuxt/content', 'nuxt-studio'],
studio: {
repository: {
provider: 'github',
owner: 'your-org',
repo: 'your-repo',
branch: 'main',
},
},
})NUXT_STUDIO_AUTH_GITHUB_CLIENT_ID=<client-id>
NUXT_STUDIO_AUTH_GITHUB_CLIENT_SECRET=<client-secret>Studio runs at /_studio by default. Supported CI providers can infer repository metadata, but authentication credentials remain explicit deployment secrets.
bc438e5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.