Install Nuxt Studio using the Nuxt CLI within your project:
npx nuxt module add nuxt-studio@alpha
When running locally, any file changes will be synchronized in real time with your local filesystem.
The publish system is only available in production mode. Use your current workflow (git command, IDE, GitHub Desktop...) to commit your changes.
While Nuxt Studio can be useful during development (especially with the upcoming Studio editor) its main advantage is the ability to publish changes directly from your production website.
In order to publish changes in production, you need to configure the git repository:
export default defineNuxtConfig({
studio: {
// Git repository configuration (owner and repo are required)
repository: {
provider: 'github', // 'github' or 'gitlab'
owner: 'your-username', // your GitHub/GitLab username or organization
repo: 'your-repo', // your repository name
branch: 'main', // the branch to commit to (default: 'main')
}
}
})
To enable this Nuxt Studio supports authentication through both GitHub and GitLab OAuth providers allowing you to log in and publish updates from production.
Once your OAuth app is setup, you should have your environment variables set in your hosting provider.
STUDIO_GITHUB_CLIENT_ID=<your_github_client_id>
STUDIO_GITHUB_CLIENT_SECRET=<your_github_client_secret>
STUDIO_GITLAB_APPLICATION_ID=<your_gitlab_application_id>
STUDIO_GITLAB_APPLICATION_SECRET=<your_gitlab_secret>
Nuxt Studio requires a server-side route for authentication.
While static generation remains supported with Nuxt hybrid rendering, your site must be deployed on a platform that supports server-side rendering (SSR) using nuxt build command.
If you want to pre-render all your pages, use the following configuration:
export default defineNuxtConfig({
nitro: {
prerender: {
// Pre-render the homepage
routes: ['/'],
// Then crawl all the links on the page
crawlLinks: true
}
}
})
Once deployed, open Studio by navigating to your configured route (default: /_studio):
CMD + . to redirect to the Studio route.Add the module to your nuxt.config.ts and configure your repository based on your Git provider:
Customize the login route using the route option:
export default defineNuxtConfig({
studio: {
route: '/admin', // default: '/_studio'
}
})
Use the repository option to specify your git repository to sync in production mode.
export default defineNuxtConfig({
studio: {
repository: {
provider: 'github', // 'github' or 'gitlab', default: 'github'
owner: 'your-username', // your GitHub/GitLab username or organization
repo: 'your-repo', // your repository name
branch: 'main', // the branch to commit to (default: main)
}
}
})
default: ''If your Nuxt Content application is in a monorepo or subdirectory, specify the rootDir option to point to the correct location.
export default defineNuxtConfig({
studio: {
repository: {
...
rootDir: 'docs'
}
}
})
default: trueBy default, Studio requests access to both public and private repositories.
Setting private: false limits the OAuth scope to public repositories only, which may be preferable for security or compliance reasons when working with public repositories.
export default defineNuxtConfig({
studio: {
repository: {
...
private: false
}
}
})
Nuxt Studio includes built-in internationalization support with the following languages available:
Set your preferred language using the i18n option:
export default defineNuxtConfig({
studio: {
i18n: {
defaultLocale: 'fr' // 'en' or 'fr'
}
}
})
This will translate:
If you want to use test locally your production setup, disable the dev option:
export default defineNuxtConfig({
studio: {
dev: false
}
})
Make sure to create another GitHub/GitLab OAuth app that redirects to your local dev server (usually http://localhost:3000).