docs: Restructure documentation to improve organization (#9578)

Author: igorlukanin

docs/.claude/commands/move-page.md

@@ -0,0 +1,27 @@
+# Move documentation page
+
+I need to move a documentation page from its current location to a new one within our documentation site. Please help me with the full process including:
+
+1. Moving the source file to the destination directory:
+  - If there's a file with the same name in the destination directory, ask for the new name and rename the source file before moving it
+  - Use the `mv` command to move the file to the new location
+
+2. Updating relevant _meta.js files to maintain proper navigation:
+  - Add the page to the destination directory's _meta.js file
+  - Remove the page from the source directory's _meta.js file
+  - If the source _meta.js file becomes empty (just contains `module.exports = {}`)
+      - Delete it
+      - Delete the directory where that _meta.js file was from the _meta.js file in its parent directory
+
+3. Finding and updating all internal references/links to the moved page:
+  - Search for references to the old URL path in all files
+  - Pay special attention to link references at the bottom of files
+  - Check plugins that might construct URLs programmatically
+
+4. Adding a redirect from the old URL to the new one:
+  - Add a new entry at the top of the redirects.json file
+  - Format should follow existing entries with "permanent": true
+
+Before starting, ask for:
+- Source page path (in URL format, e.g., /reference/configuration/environment-variables)
+- Destination page path (in URL format, e.g., /product/configuration/reference/environment-variables)

docs/CLAUDE.md

@@ -0,0 +1,81 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Repository Overview
+
+This repository contains the documentation site for Cube, a semantic layer for building data applications. The documentation is built using Next.js with the Nextra documentation theme and MDX for content authoring.
+
+## Project Structure
+
+- `/pages`: Contains all the documentation content in MDX format
+- `/components`: React components used throughout the documentation site
+  - `/common`: General UI components like buttons, logos, etc.
+  - `/layouts`: Page layout components
+  - `/mdx`: Custom components for use within MDX content
+  - `/overrides`: Components that override Nextra defaults
+- `/public`: Static assets (images, icons)
+- `/styles`: Global CSS styles
+- `/scripts`: Utility scripts for managing content
+
+## Development Commands
+
+```bash
+# Start development server
+npm run dev
+
+# Build for production
+npm run build
+
+# Start production server
+npm run start
+
+# Utility commands for content management
+npm run create-redirects     # Create redirect entries
+npm run migrate-content      # Run content migration scripts
+npm run update-links         # Update links in content files
+```
+
+## Technology Stack
+
+- **Framework**: Next.js with Nextra theme for documentation
+- **Content**: MDX (Markdown with JSX)
+- **Styling**: CSS/SCSS modules with Tailwind CSS
+- **Deployment**: Vercel
+
+## Content Organization
+
+The documentation follows a hierarchical structure:
+
+1. Main sections are defined in `/pages/_meta.js`
+2. Each section has its own `_meta.js` file that defines the order and titles of pages
+3. Content is written in MDX files with frontmatter
+
+## Component Usage in MDX
+
+The documentation uses custom MDX components for specialized content presentation:
+
+- `<AlertBox>` - For highlighting important information
+- `<CodeTabs>` - For code examples in multiple languages
+- `<Grid>` and `<GridItem>` - For creating responsive grids
+- `<YouTubeVideo>` - For embedding videos
+- `<Screenshot>` - For displaying screenshots
+
+## Best Practices
+
+1. **MDX Content**:
+   - Use the appropriate custom components for different content types
+   - Follow the existing section structure when adding new pages
+   - Include proper frontmatter with title and description
+
+2. **Component Development**:
+   - Use CSS/SCSS modules for component styling
+   - Follow the existing folder structure for new components
+   - Export components through index files for cleaner imports
+
+3. **Navigation**:
+   - Update `_meta.js` files when adding new pages to ensure proper navigation
+
+## Deployment
+
+The site is deployed to Vercel. The deployment process is automated via GitHub integration.

docs/pages/_meta.js

@@ -31,14 +31,4 @@ module.exports = {
     type: "page",
     title: "Documentation",
   },
-
-  reference: {
-    type: "page",
-    title: "Reference",
-  },
-
-  guides: {
-    type: "page",
-    title: "Guides",
-  },
 };