From 79da2532658d66d168ba3f969a6f21ad9655022f Mon Sep 17 00:00:00 2001 From: TheFlow Date: Sat, 1 Nov 2025 10:53:05 +1300 Subject: [PATCH] fix: use slug from frontmatter if present in document migration MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Previously the migration script always generated slugs from titles - Now checks metadata.slug first before auto-generating - Allows explicit slug control via frontmatter (e.g., glossary-de, glossary-fr) - Required for language-specific document API fallback to work correctly 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- scripts/migrate-documents.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/migrate-documents.js b/scripts/migrate-documents.js index b22d7ea7..714b1268 100755 --- a/scripts/migrate-documents.js +++ b/scripts/migrate-documents.js @@ -140,8 +140,8 @@ async function processMarkdownFile(filePath, sourcePath) { // Extract table of contents const tableOfContents = extractTOC(content); - // Generate slug from title - const slug = generateSlug(metadata.title); + // Use slug from frontmatter if present, otherwise generate from title + const slug = metadata.slug || generateSlug(metadata.title); // Determine if document should be public // Internal document patterns (should NOT be public)