blodemd 0.0.8 → 0.0.9

package/README.md

@@ -7,7 +7,7 @@
 </p>
 
 - **One-command deploy:** Push your entire docs folder to Blode.md with `blodemd push`.
-- **Scaffold in seconds:** Generate a ready-to-edit docs folder with `blodemd init`.
+- **Scaffold in seconds:** Generate a ready-to-edit docs folder with `blodemd new`.
 - **Config validation:** Catch `docs.json` errors before deploying.
 - **CI-friendly:** Authenticate via environment variables and use the GitHub Action for automated deploys.
 
@@ -23,13 +23,27 @@ Or run without installing:
 npx blodemd
 ```
 
-Requires Node.js 20.17+ and <25.
+Requires Node.js 20.17+.
 
 ## Quick Start
 
 ```bash
-# Scaffold a new docs folder
-blodemd init
+# Create a new docs site
+# Empty directories scaffold in place.
+# Non-empty directories get a Mint-style safety prompt.
+blodemd new
+
+# Skip prompts and use defaults
+blodemd new --yes
+
+# Scaffold the current directory explicitly
+blodemd new .
+
+# Set the project slug explicitly
+blodemd new --name acme-docs
+
+# Create the richer starter template
+blodemd new --template starter
 
 # Preview locally
 blodemd dev
@@ -44,7 +58,7 @@ blodemd push
 ## Commands
 
 ```bash
-blodemd init [dir]        Scaffold a docs folder (default: docs)
+blodemd new [directory]   Create a new blode.md documentation site
 blodemd login             Authenticate with your API key
 blodemd logout            Remove stored credentials
 blodemd whoami            Show current authentication
@@ -65,6 +79,10 @@ blodemd dev [dir]         Start the local docs preview server
 
 The CLI reads the project slug from the `name` field in `docs.json` when `--project` is not set.
 
+Interactive `blodemd new` inspects the current directory first. In an empty directory it scaffolds there and prompts for the project slug. In a non-empty directory it offers a Mint-style choice between creating a `docs/` subdirectory and scaffolding the current directory. Non-interactive runs fall back to `docs/`, and `--yes` accepts those defaults without prompting.
+
+Use `blodemd new --template starter` when you want the full starter layout with a repo README, `.gitignore`, `CLAUDE.md`, `AGENTS.md` as a symlink or pointer, SVG branding assets, and example content. The default `blodemd new` scaffold stays minimal and only writes `docs.json` plus `index.mdx`. The command stops with an error if the target directory already contains scaffolded files.
+
 ### `dev` Options
 
 ```bash
@@ -90,10 +108,8 @@ The CLI looks for a `docs.json` file in the docs directory. Minimal example:
 
 ```json
 {
-  "$schema": "https://docs.blode.md/docs.json",
+  "$schema": "https://blode.md/docs.json",
   "name": "my-project",
-  "theme": "mint",
-  "colors": { "primary": "#0D9373" },
   "navigation": {
     "groups": [{ "group": "Getting Started", "pages": ["index"] }]
   }
@@ -112,4 +128,4 @@ The package exports the `DeploymentResponse` type for use in custom deployment s
 
 ## License
 
-[MIT](../../LICENSE)
+This repository is licensed under MIT. Generated docs folders do not include a license file by default.

package/dev-server/app/[[...slug]]/page.tsx

@@ -98,6 +98,7 @@ const PreviewPage = async ({
       <ApiReference
         entry={shell.openApiEntry}
         proxyEnabled={shell.openapiProxyEnabled}
+        proxyPath="/blodemd-internal/proxy"
       />
     );
     rawContent = shell.openApiEntry.operation.description ?? "";

package/dev-server/next.config.js

@@ -1,8 +1,13 @@
 import path from "node:path";
+import { fileURLToPath } from "node:url";
 
-// When running in standalone mode (npm-installed CLI), the CLI sets this
-// to the directory containing shipped @repo packages.
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
 const packagesDir = process.env.BLODEMD_PACKAGES_DIR;
+const turbopackRoot =
+  process.env.BLODEMD_TURBOPACK_ROOT ||
+  (packagesDir
+    ? path.resolve(__dirname, "..")
+    : path.resolve(__dirname, "../.."));
 
 /** @type {import('next').NextConfig} */
 const nextConfig = {
@@ -29,17 +34,10 @@ const nextConfig = {
     "@repo/previewing",
     "@repo/validation",
   ],
-  webpack: (config) => {
-    if (packagesDir) {
-      // In standalone mode, @repo packages live in the CLI's packages/ dir.
-      // Add it as a module resolution root so webpack (and transpilePackages)
-      // can resolve @repo/common from packages/@repo/common/.
-      config.resolve.modules = [
-        path.resolve(packagesDir),
-        ...(config.resolve.modules || []),
-      ];
-    }
-    return config;
+  turbopack: {
+    // The dev server consumes sibling docs/ and workspace packages/
+    // directories, so Turbopack needs a root that includes them.
+    root: turbopackRoot,
   },
 };
 

package/dev-server/package.json

@@ -4,7 +4,7 @@
   "private": true,
   "type": "module",
   "scripts": {
-    "dev": "next dev --webpack",
+    "dev": "next dev --turbopack",
     "build": "next build",
     "start": "next start",
     "lint": "oxlint .",

package/dev-server/tsconfig.json

@@ -23,6 +23,9 @@
       ],
       "@dev/*": [
         "./*"
+      ],
+      "@repo/*": [
+        "../packages/@repo/*/src/index.ts"
       ]
     },
     "plugins": [