[docs-infra] Remove slugs from sitemap output

docs/app/docs-infra/functions/create-sitemap/page.mdx

@@ -135,7 +135,6 @@ interface SitemapSectionData {
 
 ```ts
 interface SitemapPage {
-  slug: string;
   path: string;
   title: string;
   description?: string;

docs/app/docs-infra/functions/load-precomputed-sitemap/page.mdx

@@ -200,7 +200,6 @@ The loader generates a structured data format:
         "prefix": "/docs-infra/components/",
         "pages": [
           {
-            "slug": "code-highlighter",
             "path": "./code-highlighter/page.mdx",
             "title": "Code Highlighter",
             "description": "Component for displaying code...",

docs/app/docs-infra/functions/load-server-page-index/page.mdx

@@ -41,7 +41,6 @@ const data = await loadServerPageIndex('file:///app/docs-infra/functions/page.md
 //   prefix: '/docs-infra/functions/',
 //   pages: [
 //     {
-//       slug: 'load-server-code-meta',
 //       path: './load-server-code-meta/page.mdx',
 //       title: 'Load Server Code Meta',
 //       description: 'Parses demo files to extract variant information...',
@@ -223,9 +222,8 @@ interface SitemapSectionData {
 
 ```ts
 interface SitemapPage {
-  slug: string;
-  path: string;
   title: string;
+  path: string;
   description?: string;
   keywords?: string[];
   sections?: Record<string, SitemapSection>;

docs/app/docs-infra/functions/load-server-sitemap/page.mdx

@@ -223,7 +223,6 @@ interface SitemapSectionData {
 
 ```ts
 interface SitemapPage {
-  slug: string;
   path: string;
   title: string;
   description?: string;

docs/app/docs-infra/functions/sync-page-index/page.mdx

@@ -36,7 +36,6 @@ import { syncPageIndex } from '@mui/internal-docs-infra/pipeline/syncPageIndex';
 await syncPageIndex({
   pagePath: './app/components/button/page.mdx',
   metadata: {
-    slug: 'button',
     path: './button/page.mdx',
     title: 'Button',
     description: 'A clickable button component.',
@@ -58,9 +57,9 @@ Update multiple pages in a single operation (more efficient with file locking):
 await syncPageIndex({
   pagePath: './app/components/page.mdx', // The index file itself
   metadataList: [
-    { slug: 'button', path: './button/page.mdx', title: 'Button', description: '...' },
-    { slug: 'checkbox', path: './checkbox/page.mdx', title: 'Checkbox', description: '...' },
-    { slug: 'dialog', path: './dialog/page.mdx', title: 'Dialog', description: '...' },
+    { path: './button/page.mdx', title: 'Button', description: '...' },
+    { path: './checkbox/page.mdx', title: 'Checkbox', description: '...' },
+    { path: './dialog/page.mdx', title: 'Dialog', description: '...' },
   ],
 });
 ```
@@ -187,7 +186,6 @@ Updates a parent directory's index file with page metadata.
 
 ```ts
 interface PageMetadata {
-  slug: string; // URL slug (e.g., 'button')
   path: string; // Relative path to MDX file
   title: string; // Page title
   description?: string; // Short description
@@ -220,7 +218,6 @@ Add status indicators that appear in the index list:
 await syncPageIndex({
   pagePath: './app/components/new-component/page.mdx',
   metadata: {
-    slug: 'new-component',
     path: './new-component/page.mdx',
     title: 'New Component',
     description: 'A brand new component.',
@@ -237,7 +234,6 @@ For components with API documentation, include `parts` or `exports` to make them
 await syncPageIndex({
   pagePath: './app/components/dialog/page.mdx',
   metadata: {
-    slug: 'dialog',
     path: './dialog/page.mdx',
     title: 'Dialog',
     description: 'A modal dialog component.',
@@ -265,7 +261,6 @@ For links to external resources, use `skipDetailSection`:
 await syncPageIndex({
   pagePath: './app/resources/page.mdx',
   metadata: {
-    slug: 'github',
     path: 'https://github.com/mui/base-ui',
     title: 'GitHub',
     tags: ['External'],

docs/app/docs-infra/functions/transform-markdown-metadata/page.mdx

@@ -237,8 +237,7 @@ interface SitemapSectionData {
 }
 
 interface SitemapPage {
-  title?: string;
-  slug: string;
+  title: string;
   path: string;
   description?: string;
   keywords?: string[];
@@ -673,7 +672,7 @@ To have pages automatically sorted alphabetically in your index, replace the def
 - **User-controlled ordering**: Default marker `'This file is autogenerated, but the following list can be modified.'` preserves the order you define in the editable section
 - **Automatic alphabetical**: Marker `'This file is autogenerated, but the following list can be modified. Automatically sorted alphabetically.'` sorts all pages alphabetically by title, ignoring the editable section order
 - **Case-insensitive**: Sorting uses `localeCompare()` for natural alphabetical ordering
-- **Fallback to slug**: If a page has no title, the slug is used for sorting
+- **Title required**: Every page must have a title for sorting
 
 This is useful for index pages where alphabetical order makes more sense than manual ordering, such as component libraries or API references.
 

docs/app/docs-infra/hooks/use-search/page.mdx

@@ -73,7 +73,6 @@ interface SitemapSectionData {
 
 interface SitemapPage {
   title: string;
-  slug: string;
   path: string;
   description: string;
   keywords?: string[];
@@ -293,11 +292,16 @@ Override how pages are converted to search entries:
 const { search } = useSearch({
   sitemap: () => import('./sitemap'),
   flattenPage: (page, sectionData) => {
+    const slug = page.title
+      .toLowerCase()
+      .replace(/[^a-z0-9]+/g, '-')
+      .replace(/^-+|-+$/g, '');
+
     return [
       {
         type: 'page',
         title: page.title,
-        slug: page.slug,
+        slug,
         path: page.path,
         description: page.description,
         sectionTitle: sectionData.title,

packages/docs-infra/src/createSitemap/types.ts

@@ -28,8 +28,7 @@ export interface SitemapExport {
  * Page data structure from sitemap
  */
 export interface SitemapPage {
-  title?: string;
-  slug: string;
+  title: string;
   path: string;
   description?: string;
   keywords?: string[];