chore(playground): update architecture

Author: larbish

playground/docus/content/1.getting-started/.navigation.yml

@@ -1,2 +1,2 @@
-title: Getting Started
+title: Docus
 icon: false

playground/docus/content/1.getting-started/7.essentials/.navigation.yml

@@ -0,0 +1 @@
+title: MDC

playground/docus/content/2.essentials/3.nested/1.components.md renamed to playground/docus/content/1.getting-started/7.essentials/1.components.md

@@ -0,0 +1 @@
+title: Studio

playground/docus/content/2.essentials/1.markdown-syntax.md renamed to playground/docus/content/1.getting-started/7.essentials/1.markdown-syntax.md

@@ -0,0 +1,44 @@
+---
+title: Introduction
+description: Learn what the new Nuxt Studio module is and how it differs from the previous hosted platform.
+seo:
+  title: Learn about the Nuxt Studio Open Source Module
+  description: Nuxt Studio has evolved into an open-source Nuxt module that you can self-host alongside your Nuxt Content website.
+navigation:
+  title: Introduction
+  icon: i-lucide-info
+---
+
+## The new Nuxt Studio module
+
+When NuxtLabs joined Vercel, the team promised to release [nuxt.studio](https://nuxt.studio) as a free open-source, self-hosted module for Nuxt projects.
+
+That promise is now fulfilled. Thanks to vercel support the first version of the **Nuxt Studio module** is available.
+
+You can now enable **content editing directly in production**, with real-time preview and GitHub integration, all from within your own Nuxt application.
+
+::prose-note
+**Alpha Release**
+
+:br
+
+The current version includes a Monaco code editor for Markdown, YAML, and JSON files. The visual Notion-like editor will be available in the beta release.
+::
+
+## How does it differ from the standalone platform?
+
+Originally offered as a hosted platform at [nuxt.studio](https://nuxt.studio), Studio has evolved into an open-source Nuxt module that you can deploy alongside your Nuxt Content website.
+
+This means content editors can manage and update content directly in production, without needing local development tools or Git knowledge.
+
+### Key differences
+
+- ✅ **Self-hosted** — runs entirely on your own infrastructure
+- ✅ **No external dependencies** — no APIs or third-party services required
+- ✅ **Free and open-source** — released under the MIT license
+- ✅ **Built-in integration** — works within your Nuxt app
+
+::warning
+The new Nuxt Studio module requires a server-side route for authentication.
+While static generation remains supported, your site must be **deployed on a platform that supports server-side rendering (SSR)**.
+::

playground/docus/content/2.essentials/2.code-blocks.md renamed to playground/docus/content/1.getting-started/7.essentials/2.code-blocks.md

@@ -0,0 +1,150 @@
+---
+title: Setup
+description: Learn how to install and configure Nuxt Studio to edit your content in production with GitHub authentication.
+navigation:
+  title: Setup
+  icon: i-lucide-settings
+seo:
+  title: Nuxt Studio Setup Guide
+  description: Learn how to install and configure the self-hosted Nuxt Studio module for your Nuxt Content website. Edit content in production with GitHub authentication.
+---
+
+::tip{to="https://nuxt.studio/docs/setup"}
+This documentation covers only the new open-source Nuxt Studio module.
+Click here to view the documentation for the legacy standalone platform.
+::
+
+## Install
+
+Add the Nuxt Studio module to your project:
+
+::code-group
+```bash [pnpm]
+pnpm add nuxt-studio
+```
+
+```bash [npm]
+npm install nuxt-studio
+```
+
+```bash [yarn]
+yarn add nuxt-studio
+```
+
+```bash [bun]
+bun add nuxt-studio
+```
+::
+
+Alternatively, use the Nuxt CLI to automatically add the module:
+
+```bash
+npx nuxi module add nuxt-studio
+```
+
+## Configure
+
+Add the module to your `nuxt.config.ts` and configure your GitHub repository:
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  modules: [
+    '@nuxt/content',
+    'nuxt-studio'
+  ],
+  
+  studio: {
+    // Studio admin route (default: '/_studio')
+    route: '/_studio',
+    
+    // GitHub repository configuration (required)
+    repository: {
+      provider: 'github', // only GitHub is currently supported
+      owner: 'your-username', // your GitHub username or organization
+      repo: 'your-repo', // your repository name
+      branch: 'main', // the branch to commit to
+      rootDir: '' // optional: if your Nuxt app is in a subdirectory
+    }
+  }
+})
+```
+
+::prose-tip
+If your Nuxt Content application is in a monorepo or subdirectory, specify the `rootDir` option to point to the correct location.
+::
+
+## Create GitHub OAuth App
+
+Nuxt Studio uses GitHub OAuth for authentication.
+
+::prose-steps
+> If you changed the `route` option in your config, update the callback URL accordingly (the route set instead of `/studio`)
+
+### Navigate to GitHub Developer Settings
+
+Go to [GitHub Developer Settings](https://github.com/settings/developers) and click **New OAuth App**
+
+### Configure the OAuth Application
+
+Fill in the required fields:
+
+- **Application name**: Your app name
+- **Homepage URL**: Your production website homepage URL
+- **Authorization callback URL**: `https://yourdomain.com/_studio/auth/github`:tip [If you want to try studio on project running in local, you can simply set the callback url to your local url `http://localhost:3000`.]
+
+### Copy Your Credentials
+
+After creating the OAuth app, you'll receive:
+
+- A **Client ID** (visible immediately)
+- A **Client Secret** (click **Generate a new client secret**)
+
+### Set your environment Variables
+
+Add the GitHub OAuth credentials to your deployment platform's environment variables or in your `.env` file in local
+
+```bash [.env]
+STUDIO_GITHUB_CLIENT_ID=your_github_client_id
+STUDIO_GITHUB_CLIENT_SECRET=your_github_client_secret
+```
+::
+
+## Deployment
+
+::warning
+The new Nuxt Studio module requires a server-side route for authentication.
+While static generation remains supported with [Nuxt hybrid rendering](https://nuxt.com/docs/4.x/guide/concepts/rendering#route-rules), your site must be **deployed on a platform that supports server-side rendering (SSR)**.
+::
+
+### Accessing Studio
+
+After deployment, access the Studio interface by navigating to your configured route (default: `/_studio`):
+
+1. Click **Login with GitHub** if it does not directly redirect to the OAuth app authorization page
+2. Authorize the OAuth application
+3. You'll be redirected back to Studio, ready to edit your content
+
+::prose-note
+Secure OAuth-based login with **Google** should be available quickly in the Beta release.
+::
+
+## Development mode
+
+Nuxt Studio includes an **experimental** development mode that enables real-time file system synchronization:
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  studio: {
+    development: {
+      sync: true // Enable development mode
+    }
+  }
+})
+```
+
+When enabled, Nuxt Studio will:
+
+- ✅ Write changes directly to your local `content/` directory
+- ✅ Write media changes to your local `public/` directory
+- ❌ Listen for file system changes and update the editor
+- ❌ Commit changes to your repository (use your classical workflow instead)