Refactor ObjectDocs starter template structure and update initialization scripts

Author: hotlong

examples/starter/README.md

@@ -23,24 +23,22 @@ This starter template serves multiple purposes:
 ```
 examples/starter/
 ├── content/
-│   ├── package.json          # npm scripts (auto-created by init)
-│   ├── .fumadocs/          # Site engine (created by init command, gitignored)
+│   ├── package.json          # Project configuration and scripts
+│   ├── .fumadocs/            # Site engine (created by init command, gitignored)
 │   ├── docs.site.json        # Global site configuration
+│   ├── public/               # Static assets (logos, images)
 │   └── docs/
 │       ├── meta.json         # Sidebar navigation structure
 │       ├── index.mdx         # Home page
 │       ├── getting-started.mdx
 │       └── configuration.mdx
-├── public/                   # Static assets (logos, images)
-├── package.json              # Uses @objectdocs/cli from workspace
-└── README.md                # This file
+└── README.md                 # This file
 ```
 
 **Key Points:**
-- All documentation files are in `content/`
-- `content/package.json` is auto-created by `objectdocs init`
+- All project files are in `content/`
+- `content/package.json` manages dependencies and scripts
 - `content/.fumadocs/` is gitignored and not committed
-- Root directory remains clean
 
 ## 🚀 Getting Started
 
@@ -51,44 +49,35 @@ examples/starter/
 
 ### Installation
 
-1. Navigate to the starter directory:
+1. Navigate to the content directory:
 
 ```bash
-cd examples/starter
+cd examples/starter/content
 ```
 
-2. Install the CLI:
+2. Install dependencies:
 
 ```bash
 pnpm install
 ```
 
-This will install `@objectdocs/cli` from the workspace.
-
 3. Initialize ObjectDocs:
 
 ```bash
 pnpm objectdocs init
 ```
 
 This command will:
-- Create `content/package.json` with necessary scripts
-- Copy the `@objectdocs/site` engine to `content/.fumadocs`
-- Install dependencies in `content/.fumadocs/node_modules`
+- Copy the `@objectdocs/site` engine to `.fumadocs`
+- Install dependencies in `.fumadocs/node_modules`
 - Prepare your project for development
 
 ### Development
 
 Start the development server:
 
 ```bash
-cd content && npm run dev
-```
-
-Or if you have a root-level script configured:
-
-```bash
-pnpm dev
+npm run dev
 ```
 
 The site will be available at [http://localhost:7777](http://localhost:7777).
@@ -98,29 +87,17 @@ The site will be available at [http://localhost:7777](http://localhost:7777).
 Build the project for production:
 
 ```bash
-cd content && npm run build
+npm run build
 ```
 
-Or with root-level script:
-
-```bash
-pnpm build
-```
-
-This will generate the production build in the `content/.fumadocs/.next` directory.
+This will generate the production build in the `.fumadocs/.next` directory.
 
 ### Production Server
 
 Start the production server:
 
 ```bash
-cd content && npm run start
-```
-
-Or with root-level script:
-
-```bash
-pnpm start
+npm run start
 ```
 
 ## 🌐 Deploying to Vercel
@@ -133,18 +110,18 @@ pnpm start
 npm i -g vercel
 ```
 
-2. Deploy from the examples/starter directory:
+2. Deploy from the content directory:
 
 ```bash
-cd examples/starter
+cd examples/starter/content
 vercel
 ```
 
 ### Method 2: Using GitHub Integration
 
 1. Push this starter to your GitHub repository
 2. Import the project in Vercel
-3. Set the **Root Directory** to `examples/starter`
+3. Set the **Root Directory** to `examples/starter/content`
 4. Vercel will auto-detect Next.js settings
 
 ### Vercel Configuration

examples/starter/package.json examples/starter/content/package.jsonexamples/starter/package.json renamed to examples/starter/content/package.json

@@ -4,9 +4,9 @@
   "private": true,
   "description": "Starter template for creating documentation sites with ObjectDocs",
   "scripts": {
-    "dev": "cd content && npm run dev",
-    "build": "cd content && npm run build",
-    "start": "cd content && npm run start"
+    "dev": "cd .fumadocs && npm run dev",
+    "build": "cd .fumadocs && npm run build",
+    "start": "cd .fumadocs && npm run start"
   },
   "devDependencies": {
     "@objectdocs/cli": "workspace:*"

examples/starter/public/README.md examples/starter/content/public/README.mdexamples/starter/public/README.md renamed to examples/starter/content/public/README.md

@@ -22,14 +22,14 @@ if [ ! -f "package.json" ] || ! grep -q "@objectdocs/cli" package.json; then
 fi
 
 echo "Step 1: Checking package.json configuration..."
-if grep -q '"dev": "objectdocs dev"' package.json; then
+if grep -q '"dev": "cd .fumadocs && npm run dev"' package.json; then
     echo -e "${GREEN}✓${NC} Dev script configured correctly"
 else
     echo -e "${RED}✗${NC} Dev script missing or incorrect"
     exit 1
 fi
 
-if grep -q '"build": "objectdocs build"' package.json; then
+if grep -q '"build": "cd .fumadocs && npm run build"' package.json; then
     echo -e "${GREEN}✓${NC} Build script configured correctly"
 else
     echo -e "${RED}✗${NC} Build script missing or incorrect"
@@ -46,14 +46,14 @@ fi
 echo ""
 echo "Step 2: Checking content structure..."
 
-if [ -d "content/docs" ]; then
+if [ -d "docs" ]; then
     echo -e "${GREEN}✓${NC} Content directory exists"
 else
     echo -e "${RED}✗${NC} Content directory missing"
     exit 1
 fi
 
-if [ -f "content/docs.site.json" ]; then
+if [ -f "docs.site.json" ]; then
     echo -e "${GREEN}✓${NC} Site configuration exists"
 else
     echo -e "${RED}✗${NC} Site configuration missing"

examples/starter/validate.sh examples/starter/content/validate.shexamples/starter/validate.sh renamed to examples/starter/content/validate.sh

@@ -2,7 +2,7 @@
   "$schema": "https://openapi.vercel.sh/vercel.json",
   "buildCommand": "pnpm build",
   "devCommand": "pnpm dev",
-  "installCommand": "pnpm install",
+  "installCommand": "pnpm install && pnpm objectdocs init",
   "framework": "nextjs",
-  "outputDirectory": ".next"
+  "outputDirectory": ".fumadocs/.next"
 }

examples/starter/vercel.json examples/starter/content/vercel.jsonexamples/starter/vercel.json renamed to examples/starter/content/vercel.json

@@ -22,7 +22,12 @@ export function registerInitCommand(cli) {
     .action(async (options) => {
       console.log('Initializing ObjectDocs...\n');
 
-      const contentDir = path.resolve(process.cwd(), 'content');
+      let contentDir = path.resolve(process.cwd(), 'content');
+      // Support running from inside 'content' directory
+      if (!fs.existsSync(contentDir) && fs.existsSync(path.resolve(process.cwd(), 'docs'))) {
+        contentDir = process.cwd();
+      }
+
       const targetDir = path.resolve(contentDir, '.fumadocs');
       const contentPackageJsonPath = path.resolve(contentDir, 'package.json');