@karaoke-cms/create 0.9.3 → 0.9.6

package/README.md

@@ -1,10 +1,8 @@
 # @karaoke-cms/create
 
-Scaffolding tool for karaoke-cms. Creates a complete new project from scratch with a single command.
+Scaffolding tool for karaoke-cms. Creates a complete new project from scratch with a single command, then optionally deploys a live preview to Cloudflare Pages.
 
-## Where it belongs
-
-`packages/create/` in the monorepo. Published to npm as `@karaoke-cms/create` and invoked via npm's `create` shorthand:
+## Usage
 
 ```bash
 npm create @karaoke-cms@latest
@@ -12,37 +10,26 @@ npm create @karaoke-cms@latest
 npm create @karaoke-cms@latest my-site
 ```
 
-This resolves to running `packages/create/src/index.js` via the `create-karaoke-cms` bin entry.
-
-## What it does
+The wizard asks for your project name, site title, URL, and description, then generates everything and installs dependencies.
 
-Runs an interactive CLI that prompts for project configuration, then generates a complete project directory:
+At the end you're offered a one-step deploy to Cloudflare Pages (defaults to **yes** — your site can be live before you open your code editor).
 
-**Prompts:**
-1. Project directory name
-2. Site title
-3. Site URL (for sitemap and OG tags)
-4. Description
-5. Theme (`default`, `minimal`, or `blog`)
-6. Enable Pagefind search? (y/n)
-7. Enable Giscus comments? (y/n) — if yes, prompts for repo, repoId, category, categoryId
+## What gets created
 
-**Generated files:**
 ```
 my-site/
-  package.json           # deps pinned to same version as create package
-  astro.config.mjs       # site URL, karaoke() integration
-  karaoke.config.ts      # title, description, theme, modules, vault path
+  package.json          # @karaoke-cms/* deps pinned to current version
+  astro.config.mjs      # karaoke() integration, site URL
+  karaoke.config.ts     # title, description, theme, blog module
   src/
-    content.config.ts    # makeCollections() wired to vault/
-    env.d.ts             # /// <reference types="@karaoke-cms/astro/client" />
+    content.config.ts   # makeCollections() wired to vault/
+    env.d.ts            # TypeScript types for virtual:karaoke-cms/config
   tsconfig.json
   .gitignore
-  .env.default           # KARAOKE_VAULT=./vault/
-  public/
-    _redirects           # Cloudflare Pages 404 config
-  vault/                 # Obsidian vault with sample blog post and doc
-    blog/
+  .env.default          # KARAOKE_VAULT=./vault/
+  public/_redirects     # Cloudflare Pages 404 config
+  vault/                # Obsidian vault with sample blog posts
+    blog/               # 30 demo posts (publish: true)
     docs/
     karaoke-cms/
       config/
@@ -50,27 +37,46 @@ my-site/
         menus.yaml
 ```
 
-After scaffolding, `git init` + initial commit runs automatically if `git` is available.
+A git repository is initialised with an initial commit. Opening `vault/` in Obsidian lets you write content immediately.
 
-## How to use
+## Generated karaoke.config.ts
 
-```bash
-npm create @karaoke-cms@latest
+```ts
+import { defineConfig } from '@karaoke-cms/astro';
+import { blog } from '@karaoke-cms/module-blog';
+import { themeDefault } from '@karaoke-cms/theme-default';
+import { loadEnv } from '@karaoke-cms/astro/env';
+
+const env = loadEnv(new URL('.', import.meta.url));
 
+export default defineConfig({
+  vault: env.KARAOKE_VAULT,
+  title: 'My Site',
+  description: 'What this site is about.',
+  modules: [blog({ mount: '/blog' })],
+  theme: themeDefault(),
+});
+```
+
+## Local dev
+
+```bash
 cd my-site
-npm install
 npm run dev     # → http://localhost:4321
 ```
 
-Open `my-site/vault/` in Obsidian to write content. Files with `publish: true` in frontmatter appear on the live site.
+## Deploy
 
-Zero runtime dependencies — the scaffolder uses Node.js built-ins only.
+```bash
+npm run deploy  # publishes to Cloudflare Pages
+```
 
-## How it changes the behavior of the system
+Requires a Cloudflare account and the `wrangler` CLI. The wizard handles the first deploy interactively.
 
-The create package is not imported by running sites — it only runs once at project setup time. Its output determines:
+## What's new in 0.9.5
 
-- Which version of `@karaoke-cms/astro` and the theme packages are installed (pinned to the same version as the create package, since packages ship in lockstep)
-- The initial `karaoke.config.ts` shape: which theme, which modules, vault location
-- The initial vault structure: two sample posts so the site is not empty on first `dev`
-- Whether search and comments infrastructure is included in `karaoke.config.ts`
+- **Deploy defaults to yes** — the Cloudflare Pages deploy prompt now defaults to YES, so new sites are live by the end of the wizard
+- **Three success screens** — distinct output for deploy success, declined, and failed (failed surfaces the error and next steps)
+- **isTTY color guard** — ANSI color codes are disabled in CI and piped output
+- **30 demo blog posts** included in the scaffolded vault so the site is populated on first visit
+- **Generated `karaoke.config.ts`** uses `themeDefault()` + `blog()` module API (replaces the old string-based theme config)

package/karaoke-create-vault/.obsidian/workspace.json

@@ -20,23 +20,8 @@
               "icon": "lucide-file",
               "title": "getting-started"
             }
-          },
-          {
-            "id": "52e565c48d7a7c39",
-            "type": "leaf",
-            "state": {
-              "type": "markdown",
-              "state": {
-                "file": "karaoke-cms/manual/deployment.md",
-                "mode": "source",
-                "source": false
-              },
-              "icon": "lucide-file",
-              "title": "deployment"
-            }
           }
-        ],
-        "currentTab": 1
+        ]
       }
     ],
     "direction": "vertical"
@@ -183,10 +168,10 @@
             "state": {
               "type": "file-properties",
               "state": {
-                "file": "karaoke-cms/manual/deployment.md"
+                "file": "docs/getting-started.md"
               },
               "icon": "lucide-info",
-              "title": "File properties for deployment"
+              "title": "File properties for getting-started"
             }
           }
         ],
@@ -208,8 +193,9 @@
       "templater-obsidian:Templater": false
     }
   },
-  "active": "52e565c48d7a7c39",
+  "active": "d663da17c7b12a45",
   "lastOpenFiles": [
+    "karaoke-cms/manual/deployment.md",
     "karaoke-cms/manual/configuration.md",
     "karaoke-cms/templates/index.md",
     "karaoke-cms/config/index.md",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@karaoke-cms/create",
   "type": "module",
-  "version": "0.9.3",
+  "version": "0.9.6",
   "description": "Scaffold a new karaoke-cms project",
   "bin": {
     "create-karaoke-cms": "./src/index.js"

package/src/index.js

@@ -17,12 +17,13 @@ import {
 } from './templates.js';
 
 // ── ANSI helpers ─────────────────────────────────────────────────────────────
-const R = '\x1b[0m';
-const BOLD = '\x1b[1m';
-const GREEN = '\x1b[32m';
-const CYAN = '\x1b[36m';
-const GRAY = '\x1b[90m';
-const RED = '\x1b[31m';
+const NO_COLOR = !process.stdout.isTTY;
+const R     = NO_COLOR ? '' : '\x1b[0m';
+const BOLD  = NO_COLOR ? '' : '\x1b[1m';
+const GREEN = NO_COLOR ? '' : '\x1b[32m';
+const CYAN  = NO_COLOR ? '' : '\x1b[36m';
+const GRAY  = NO_COLOR ? '' : '\x1b[90m';
+const RED   = NO_COLOR ? '' : '\x1b[31m';
 
 // Use create package's own version as the @karaoke-cms/astro dep range
 // (packages ship in lockstep)
@@ -174,34 +175,40 @@ async function main() {
   }
 
   // ── npm install ──────────────────────────────────────────────────────────────
-  console.log(`\n  Installing dependencies...\n`);
+  console.log(`\n  Installing dependencies... ${GRAY}(this may take a minute)${R}\n`);
   const installResult = spawnSync('npm', ['install'], { cwd: targetDir, stdio: 'inherit' });
   if (installResult.status !== 0) {
     console.log(`  ${GRAY}(install failed — run npm install manually)${R}`);
   }
 
   // ── Deploy prompt ────────────────────────────────────────────────────────────
-  const deployNow = await askYesNo('Publish a live preview to Cloudflare Pages now?', false);
-
-  rl.close();
+  const deployNow = await askYesNo('Publish a live preview to Cloudflare Pages now?', true);
 
   let liveUrl = null;
+  let deployFailed = false;
   if (deployNow) {
     const projectName = `${slugify(dir)}-preview`;
     liveUrl = await deployToCloudflare(targetDir, projectName);
+    if (!liveUrl) deployFailed = true;
   }
 
+  rl.close();
+
   // ── Success screen ───────────────────────────────────────────────────────────
-  console.log(`\n${GREEN}✓${R} Done! Created ${BOLD}${dir}/${R}\n`);
+  const failNote = deployFailed ? `  ${GRAY}(deploy failed — see above)${R}` : '';
+  console.log(`\n${GREEN}✓${R} Done! Created ${BOLD}${dir}/${R}${failNote}\n`);
   if (liveUrl) {
-    console.log(`  ${BOLD}🎤 Live:${R}      ${liveUrl}`);
-    console.log(`  ${BOLD}💻 Dev:${R}       ${CYAN}cd ${dir} && npm run dev${R}`);
+    console.log(`  ${BOLD}🎤 Live URL:${R}  ${GREEN}${liveUrl}${R}`);
+    console.log(`  ${BOLD}💻 Local dev:${R} ${CYAN}cd ${dir} && npm run dev${R}`);
     console.log(`  ${BOLD}🔄 Redeploy:${R}  ${CYAN}npm run deploy${R}\n`);
+  } else if (deployFailed) {
+    console.log(`  The project is ready. Fix the error above, then:`);
+    console.log(`  ${CYAN}cd ${dir}${R}`);
+    console.log(`  ${CYAN}npm run deploy${R}  ${GRAY}→ retry publishing to Cloudflare Pages${R}\n`);
   } else {
-    console.log(`  Next steps:\n`);
     console.log(`  ${CYAN}cd ${dir}${R}`);
-    console.log(`  ${CYAN}npm run dev${R}    ${GRAY}→ http://localhost:4321${R}`);
-    console.log(`  ${CYAN}npm run deploy${R} ${GRAY}→ publish to Cloudflare Pages${R}\n`);
+    console.log(`  ${CYAN}npm run dev${R}    ${GRAY}→ start local dev server${R}`);
+    console.log(`  ${CYAN}npm run deploy${R} ${GRAY}→ publish to Cloudflare Pages when ready${R}\n`);
   }
   console.log(`  ${GRAY}Open ${BOLD}${dir}/vault/${R}${GRAY} in Obsidian to write content.${R}\n`);
 }
@@ -230,7 +237,7 @@ export async function deployToCloudflare(targetDir, projectName) {
   }
 
   // 2. Build
-  console.log(`  ${CYAN}Building...${R}`);
+  console.log(`  ${CYAN}Building... ${GRAY}(15–30 seconds)${R}`);
   const build = spawnSync('npm', ['run', 'build'],
     { cwd: targetDir, stdio: 'inherit' });
   if (build.status !== 0) {
@@ -261,9 +268,13 @@ export async function deployToCloudflare(targetDir, projectName) {
   const liveUrl = `https://${projectName}.pages.dev`;
 
   // 6. Write real URL back to astro.config.mjs (replaces placeholder set during scaffold)
-  const configPath = join(targetDir, 'astro.config.mjs');
-  const configSrc = readFileSync(configPath, 'utf8');
-  writeFileSync(configPath, configSrc.replace('https://your-site.pages.dev', liveUrl));
+  try {
+    const configPath = join(targetDir, 'astro.config.mjs');
+    const configSrc = readFileSync(configPath, 'utf8');
+    writeFileSync(configPath, configSrc.replace('https://your-site.pages.dev', liveUrl));
+  } catch {
+    console.log(`  ${GRAY}Could not update site URL — edit astro.config.mjs manually.${R}`);
+  }
 
   return liveUrl;
 }

package/src/templates.js

@@ -75,32 +75,28 @@ export default defineConfig({
  *   title: string,
  *   description: string,
  *   theme: string,
- *   search: boolean,
  *   comments: { repo: string, repoId: string, category: string, categoryId: string } | null,
  * }} opts
  */
-export function karaokeConfig({ title, description, theme, search, comments }) {
-  const modules = {};
-  if (search) modules.search = { enabled: true };
-  if (comments) modules.comments = { enabled: true, ...comments };
-
-  const modulesStr = Object.keys(modules).length > 0
-    ? `\n  modules: ${JSON.stringify(modules, null, 2).replace(/\n/g, '\n  ')},`
+export function karaokeConfig({ title, description, theme, comments }) {
+  const commentsStr = comments
+    ? `\n  comments: ${JSON.stringify({ enabled: true, ...comments }, null, 2).replace(/\n/g, '\n  ')},`
     : '';
 
-  return `import type { KaraokeConfig } from '@karaoke-cms/astro';
+  return `import { defineConfig } from '@karaoke-cms/astro';
+import { blog } from '@karaoke-cms/module-blog';
+import { themeDefault } from '@karaoke-cms/theme-default';
 import { loadEnv } from '@karaoke-cms/astro/env';
 
 const env = loadEnv(new URL('.', import.meta.url));
 
-const config: KaraokeConfig = {
+export default defineConfig({
   vault: env.KARAOKE_VAULT,
   title: ${JSON.stringify(title)},
   description: ${JSON.stringify(description)},
-  theme: ${JSON.stringify(theme)},${modulesStr}
-};
-
-export default config;
+  modules: [blog({ mount: '/blog' })],
+  theme: themeDefault(),${commentsStr}
+});
 `;
 }
 

package/karaoke-create-vault/karaoke-cms/config/collections.yaml

@@ -1,10 +0,0 @@
-collections:
-  blog:
-    modes: [dev, prod]
-    label: Blog
-  docs:
-    modes: [dev, prod]
-    label: Docs
-  karaoke-cms:
-    modes: [dev]
-    label: Handbook

package/karaoke-create-vault/karaoke-cms/config/index.md

@@ -1,14 +0,0 @@
----
-title: "Config"
----
-
-# Config
-
-Configuration files for your karaoke-cms vault.
-
-| File | Purpose |
-|------|---------|
-| `collections.yaml` | Which collections are visible in dev vs production |
-| `menus.yaml` | Site navigation: header menu, footer columns, and their entries |
-
-Edit these files to change what appears on your site and in the navigation. Changes take effect on the next dev server restart or build.

package/karaoke-create-vault/karaoke-cms/config/menus.yaml

@@ -1,58 +0,0 @@
-# menus.yaml — define named menus for your site.
-#
-# Each menu has an orientation (horizontal or vertical) and a list of entries.
-# Entries are sorted by weight (ascending). Submenus are defined by nesting entries.
-#
-# when: collection:name — hide entry when the collection is disabled or has no
-#                         published posts. Omit `when` to always show.
-#
-# If this file is absent, karaoke-cms generates a default main menu (Blog/Docs/Tags)
-# and a default footer menu (RSS) from your active collections.
-
-menus:
-  main:
-    orientation: horizontal
-    entries:
-      - text: Blog
-        href: /blog
-        weight: 10
-        when: collection:blog
-      - text: Docs
-        href: /docs
-        weight: 20
-        when: collection:docs
-      - text: Tags
-        href: /tags
-        weight: 30
-      - text: karaoke-cms
-        href: /karaoke-cms
-        weight: 40
-        when: collection:karaoke-cms
-
-  footer-2:
-    orientation: vertical
-    entries:
-      - text: karaoke-cms
-        href: /karaoke-cms/manual/index
-        weight: 10
-        when: collection:karaoke-cms
-        entries:
-          - text: Manual
-            href: /karaoke-cms/manual/index
-            weight: 10
-            when: collection:karaoke-cms
-          - text: Config
-            href: /karaoke-cms/config/index
-            weight: 20
-            when: collection:karaoke-cms
-          - text: Templates
-            href: /karaoke-cms/templates/index
-            weight: 30
-            when: collection:karaoke-cms
-
-  footer:
-    orientation: vertical
-    entries:
-      - text: RSS
-        href: /rss.xml
-        weight: 10

package/karaoke-create-vault/karaoke-cms/manual/configuration.md

@@ -1,77 +0,0 @@
----
-title: "Configuration"
----
-
-# Configuration
-
-> **Handbook — dev only.**
-
-## karaoke.config.ts
-
-The main config file at your project root. TypeScript — fully typed.
-
-```ts
-import type { KaraokeConfig } from '@karaoke-cms/astro';
-
-const config: KaraokeConfig = {
-  title: "My Site",
-  description: "What this site is about.",
-  theme: "default",         // "default" | "minimal"
-  modules: {
-    search: {
-      enabled: true,        // Pagefind full-text search
-    },
-    comments: {
-      enabled: true,        // Giscus (GitHub Discussions)
-      repo: "owner/repo",
-      repoId: "R_...",
-      category: "General",
-      categoryId: "DIC_...",
-    },
-  },
-};
-
-export default config;
-```
-
-Get Giscus values from [giscus.app](https://giscus.app) after enabling Discussions on your repo.
-
-## collections.yaml
-
-`content/karaoke-cms/config/collections.yaml` controls which collections are visible in dev vs prod:
-
-```yaml
-collections:
-  blog:
-    modes: [dev, prod]   # visible in both dev and production
-    label: Blog
-  docs:
-    modes: [dev, prod]
-    label: Docs
-  karaoke-cms:
-    modes: [dev]         # dev-only — never ships
-    label: Handbook
-```
-
-To add a custom collection (e.g., `content/notes/`):
-
-```yaml
-collections:
-  notes:
-    modes: [dev, prod]
-    label: Notes
-```
-
-## Layout regions
-
-Place UI components in the sidebar or header via `karaoke.config.ts`:
-
-```ts
-layout: {
-  regions: {
-    right: { components: ['recent-posts'] },
-  },
-},
-```
-
-Available components: `header`, `main-menu`, `search`, `recent-posts`, `footer`.

package/karaoke-create-vault/karaoke-cms/manual/content.md

@@ -1,38 +0,0 @@
----
-title: "Writing Content"
----
-
-# Writing Content
-
-> **Handbook — dev only.**
-
-## Frontmatter fields
-
-```yaml
----
-title: "My Post"            # required — build fails without it
-publish: true               # required to appear on site (default: false)
-date: 2026-01-15            # optional — YYYY-MM-DD, used for sorting
-author: "Name"              # optional — string or array ["Alice", "Bob"]
-description: "..."          # optional — used in OG meta tags and RSS
-tags: [writing, tutorial]   # optional — enables tag pages at /tags/[tag]
----
-```
-
-## Privacy model
-
-Every file is **private by default**. `publish: false` (or a missing `publish` field) means the file stays in your vault and never enters the build — not in HTML, not in RSS, not in the sitemap, not in the Pagefind search index.
-
-Only `publish: true` files appear on your site.
-
-## Wikilinks
-
-Use `[[slug]]` syntax to link between notes. karaoke-cms resolves wikilinks automatically:
-
-- `[[blog/hello-world]]` → `/blog/hello-world/`
-- `[[docs/getting-started]]` → `/docs/getting-started/`
-- `[[docs/getting-started|Getting Started]]` → link text "Getting Started"
-
-## AI enrichment (optional)
-
-Run `npx @karaoke-cms/enrich` to auto-generate `tags`, `description`, and `reading_time` for published notes using OpenAI or Anthropic. Skips already-enriched notes via a local cache.

package/karaoke-create-vault/karaoke-cms/manual/deployment.md

@@ -1,46 +0,0 @@
----
-title: "Deployment"
----
-
-# Deployment
-
-> **Handbook — dev only.**
-
-## Cloudflare Pages (recommended)
-
-1. Push your project to a GitHub repo
-2. Go to [Cloudflare Pages](https://pages.cloudflare.com) → Create a project → Connect to your repo
-3. Build settings:
-   - **Build command:** `npm run build`
-   - **Build output directory:** `dist`
-   - **Node.js version:** 22
-4. Deploy
-
-On every push to `main`, Cloudflare Pages rebuilds and redeploys automatically.
-
-## GitHub Actions (privacy gate)
-
-The included `deploy.yml` workflow runs `assert-privacy` on every build to verify that no private content leaks into `dist/`. If a private note accidentally gets into the build, the deploy fails before it reaches production.
-
-## Custom domain
-
-In Cloudflare Pages → your project → Custom domains → Add a domain. Update `site:` in `astro.config.mjs` to match:
-
-```js
-export default defineConfig({
-  site: 'https://your-domain.com',
-  // ...
-});
-```
-
-## Environment variables
-
-If you use `@karaoke-cms/enrich` in CI:
-
-| Variable | Purpose |
-|----------|---------|
-| `OPENAI_API_KEY` | Required if `ENRICH_PROVIDER=openai` (default) |
-| `ANTHROPIC_API_KEY` | Required if `ENRICH_PROVIDER=anthropic` |
-| `ENRICH_ENABLED` | Set to `true` to enable AI enrichment in CI |
-| `CLOUDFLARE_API_TOKEN` | For Cloudflare Pages deploy via GitHub Actions |
-| `CLOUDFLARE_ACCOUNT_ID` | For Cloudflare Pages deploy via GitHub Actions |

package/karaoke-create-vault/karaoke-cms/manual/index.md

@@ -1,41 +0,0 @@
----
-title: "Handbook"
----
-
-# karaoke-cms Handbook
-
-> **Handbook — dev only.** This section is visible at `/karaoke-cms` in dev mode and never ships to production.
-
-karaoke-cms is an Astro framework for publishing Obsidian vaults as static sites. Private-by-default: only files with `publish: true` in frontmatter appear on your site.
-
-## How it works
-
-```
-Obsidian vault (this directory)
-  ↓  write notes with publish: true
-  ↓  push to main
-  ↓  GitHub Actions: astro build + assert-privacy
-  ↓  Cloudflare Pages
-  ↓  live site
-```
-
-Your vault is also your deploy pipeline config, your documentation, and your content collection — all in one place.
-
-## Handbook sections
-
-- [[content]] — Writing content and frontmatter
-- [[configuration]] — karaoke.config.ts reference
-- [[deployment]] — Deploying to Cloudflare Pages
-- [[privacy]] — How publish:true works
-
-## Collections
-
-This vault has three content collections:
-
-| Collection | Mode | Purpose |
-|------------|------|---------|
-| `blog/` | dev + prod | Published blog posts |
-| `docs/` | dev + prod | Published documentation |
-| `karaoke-cms/` | dev only | This handbook — never ships |
-
-Edit `content/karaoke-cms/config/collections.yaml` to add your own collections or change their visibility.

package/karaoke-create-vault/karaoke-cms/manual/privacy.md

@@ -1,37 +0,0 @@
----
-title: "Privacy"
----
-
-# Privacy Model
-
-> **Handbook — dev only.**
-
-## The rule
-
-**Every file is private by default.** Only files with `publish: true` in frontmatter appear on your site.
-
-A file without `publish: true` never enters the build — not in HTML, RSS, sitemap, or the Pagefind search index.
-
-## How it's enforced
-
-Two independent layers:
-
-1. **Astro content filter** — `getCollection('blog', ({ data }) => data.publish === true)` filters at the query level. Pages only receive published entries.
-
-2. **assert-privacy** — a post-build check that scans `dist/` for known private note titles and content. If any private content leaks, the build fails before deploy.
-
-The collection mode system adds a third layer: `karaoke-cms/` is excluded from `makeCollections()` in production entirely. Even if a handbook page had `publish: true`, it would never enter the prod build graph.
-
-## What "private" means
-
-| Field | Builds? | Searchable? | In RSS? | In sitemap? |
-|-------|---------|-------------|---------|-------------|
-| `publish: true` | Yes | Yes | Yes | Yes |
-| `publish: false` | No | No | No | No |
-| missing | No | No | No | No |
-
-## Audit your site
-
-After every build, `assert-privacy.js` outputs a summary of what shipped. Check it in your CI logs.
-
-For a manual check: `node node_modules/@karaoke-cms/assert-privacy/dist/index.js dist`

package/karaoke-create-vault/karaoke-cms/templates/blog-header.md

@@ -1,9 +0,0 @@
----
-title: ""            # required — build fails without it
-publish: false               # required to appear on site (default: false)
-date: 2026-01-15            # optional — YYYY-MM-DD, used for sorting
-author: ""              # optional — string or array ["Alice", "Bob"]
-description: ""          # optional — used in OG meta tags and RSS
-tags: [general]   # optional — enables tag pages at /tags/[tag]
-notetype: blog
----

package/karaoke-create-vault/karaoke-cms/templates/docs-header.md

@@ -1,9 +0,0 @@
----
-title: ""            # required — build fails without it
-publish: false               # required to appear on site (default: false)
-date: 2026-01-15            # optional — YYYY-MM-DD, used for sorting
-author: ""              # optional — string or array ["Alice", "Bob"]
-description: ""          # optional — used in OG meta tags and RSS
-tags: [general]   # optional — enables tag pages at /tags/[tag]
-notetype: blog
----

package/karaoke-create-vault/karaoke-cms/templates/index-by-foldernote.md

@@ -1,8 +0,0 @@
----
-title: ""            # required — build fails without it
-publish: false               # required to appear on site (default: false)
-date: 2026-01-15            # optional — YYYY-MM-DD, used for sorting
-author: ""              # optional — string or array ["Alice", "Bob"]
-description: "..."          # optional — used in OG meta tags and RSS
-tags: [general]   # optional — enables tag pages at /tags/[tag]
----

package/karaoke-create-vault/karaoke-cms/templates/index.md

@@ -1,15 +0,0 @@
----
-title: "Templates"
----
-
-# Templates
-
-Obsidian templates for common note types. Use with the [Templater](https://github.com/SilentVoid13/Templater) plugin.
-
-| Template | Use for |
-|----------|---------|
-| `blog-header.md` | New blog posts — sets `title`, `date`, `publish: false` |
-| `docs-header.md` | New documentation pages |
-| `index-by-foldernote.md` | Folder index notes (requires the folder-notes Obsidian plugin) |
-
-In Templater settings, set the template folder to `karaoke-cms/templates`.