Docs v2 Preview [Public Link]

.cursorrules

@@ -0,0 +1,45 @@
+# Cursor Rules for Livepeer Documentation
+
+## MANDATORY: Read Style Guide Before Making Changes
+
+**BEFORE making any code, styling, or component changes, you MUST read:**
+- `v2/pages/07_resources/documentation-guide/style-guide.mdx` - Production-grade styling guidelines
+- `v2/pages/07_resources/documentation-guide/component-library.mdx` - Component reference
+
+## Critical Styling Rules
+
+1. **USE CSS Custom Properties ONLY** - Never use ThemeData or hardcode colors
+   - ✅ Use: `var(--accent)`, `var(--text)`, `var(--card-background)`
+   - ❌ Never use: `ThemeData.light.accent` or hardcoded hex colors
+
+2. **Mintlify Gotchas** - Read the style guide for all Mintlify limitations:
+   - Import paths must be absolute from root
+   - Cannot import into component files
+   - JSX files cannot import other JSX files
+   - React hooks are global (no imports needed)
+
+3. **Component Usage** - Always check component library before creating new components
+
+## Repository Structure
+
+- `v2/pages/` - Current documentation pages (MDX)
+- `snippets/components/` - Custom React/JSX components
+- `snippets/data/` - Reusable data files
+- `style.css` - Global CSS Custom Properties for theming
+- `docs.json` - Mintlify navigation configuration
+
+## Before Making Changes
+
+1. Read the style guide: `v2/pages/07_resources/documentation-guide/style-guide.mdx`
+2. Check component library: `v2/pages/07_resources/documentation-guide/component-library.mdx`
+3. Review Mintlify gotchas in style guide
+4. Use existing components when possible
+5. Follow CSS Custom Properties for all styling
+
+## Documentation Standards
+
+- Use CSS Custom Properties for all theme-aware colors
+- Follow Mintlify import patterns (absolute paths from root)
+- Test in both light and dark modes
+- No suggestions or recommendations in production docs
+- Keep production docs factual only

.githooks/BYPASS.md

@@ -0,0 +1,129 @@
+# Pre-Commit Hook Bypass Flags
+
+The pre-commit hook can be bypassed using environment variables. **Use these flags sparingly and only when necessary.**
+
+## Human-Only Override Flag
+
+### `ALLOW_WHITELIST_EDIT=1` ⚠️ HUMANS ONLY
+
+**CRITICAL:** The `.whitelist` file is **PROTECTED** and cannot be edited by AI agents. The file contains the explicit rule: "IF YOU ARE AN AI YOU ARE ABSOLUTELY NOT ALLOWED TO EDIT THIS FILE."
+
+**This flag is for HUMANS ONLY. AI agents must never use this flag.**
+
+**Usage (HUMANS ONLY):**
+```bash
+ALLOW_WHITELIST_EDIT=1 git commit -m "Update .whitelist to add new root file"
+```
+
+**What it does:**
+- Allows editing the `.whitelist` file
+- Shows a warning that the flag should only be used by humans
+- Still runs all other pre-commit checks
+
+**⚠️ WARNING:** AI agents are explicitly forbidden from using this flag. Only human users may edit `.whitelist`.
+
+## Available Flags
+
+### `SKIP_STRUCTURE_CHECK=1`
+Bypasses structure validation checks:
+- Root directory whitelist enforcement
+- Snippets directory structure checks
+- v1/ frozen directory protection
+
+**Usage:**
+```bash
+SKIP_STRUCTURE_CHECK=1 git commit -m "Emergency fix"
+```
+
+### `SKIP_STYLE_CHECK=1`
+Bypasses style guide compliance checks:
+- ThemeData usage checks
+- Hardcoded color checks
+- Relative import checks
+- React/Mintlify import checks
+
+**Usage:**
+```bash
+SKIP_STYLE_CHECK=1 git commit -m "Temporary style change"
+```
+
+### `SKIP_VERIFICATION=1`
+Bypasses verification scripts:
+- MDX syntax validation
+- JSON syntax validation
+- Shell script validation
+- JavaScript/JSX validation
+- Mintlify configuration checks
+- Import path validation
+
+**Usage:**
+```bash
+SKIP_VERIFICATION=1 git commit -m "Skip verification"
+```
+
+### `SKIP_TESTS=1`
+Bypasses test suite execution:
+- Unit tests
+- Integration tests
+- Browser tests
+
+**Usage:**
+```bash
+SKIP_TESTS=1 git commit -m "Skip tests"
+```
+
+### `SKIP_ALL=1`
+Bypasses ALL checks. **Use with extreme caution!**
+
+**Usage:**
+```bash
+SKIP_ALL=1 git commit -m "Emergency commit - all checks bypassed"
+```
+
+## When to Use Bypass Flags
+
+### ✅ Acceptable Use Cases:
+- **Emergency hotfixes** - Critical production issues
+- **WIP commits** - Work in progress that will be fixed before merge
+- **Temporary debugging** - Adding debug code that will be removed
+- **Migration work** - During active migration when structure is intentionally changing
+
+### ❌ NOT Acceptable:
+- **Regular commits** - Normal development should pass all checks
+- **Permanent bypass** - Don't make bypassing a habit
+- **Skipping to avoid fixing issues** - Fix the issues instead
+
+## Best Practices
+
+1. **Fix issues instead of bypassing** - Bypass flags are for emergencies, not convenience
+2. **Document why** - If you must bypass, explain why in the commit message
+3. **Follow up** - If you bypassed checks, fix the issues in a follow-up commit
+4. **Review carefully** - If bypassing, manually verify your changes are correct
+
+## Examples
+
+### Emergency Hotfix
+```bash
+SKIP_ALL=1 git commit -m "HOTFIX: Critical security patch - bypassing checks for speed"
+```
+
+### WIP Commit
+```bash
+SKIP_STYLE_CHECK=1 git commit -m "WIP: Adding feature - will fix style issues before merge"
+```
+
+### Migration Work
+```bash
+SKIP_STRUCTURE_CHECK=1 git commit -m "Migration: Moving files - structure intentionally changing"
+```
+
+## Warning
+
+Bypassing pre-commit hooks can lead to:
+- Broken builds
+- Style violations
+- Structure violations
+- Broken pages
+- Merge conflicts
+
+**Always verify your changes work correctly after bypassing checks.**

.githooks/README.md

@@ -0,0 +1,95 @@
+# Git Hooks - Quick Reference
+
+This directory contains git hooks for enforcing repository standards.
+
+**📖 Full Documentation:** See [docs/CONTRIBUTING/GIT-HOOKS.md](../../docs/CONTRIBUTING/GIT-HOOKS.md)
+
+## Quick Start
+
+```bash
+# Install hooks
+./.githooks/install.sh
+```
+
+## Pre-commit Hook
+
+The pre-commit hook enforces style guide compliance and runs verification scripts:
+
+### Style Guide Checks
+
+- ❌ **ThemeData usage** - Blocks deprecated ThemeData imports
+- ❌ **Hardcoded colors** - Warns about hardcoded hex colors that should use CSS variables
+- ⚠️ **Relative imports** - Warns about relative imports (should use absolute paths)
+- ⚠️ **@mintlify/components imports** - Warns about unnecessary imports (components are global)
+- ⚠️ **React hook imports** - Warns about unnecessary React imports (hooks are global)
+
+### Verification Scripts
+
+The hook also runs `.githooks/verify.sh` which checks:
+
+- ✅ **MDX syntax** - Validates frontmatter and basic MDX structure
+- ✅ **JSON syntax** - Validates JSON files are parseable
+- ✅ **Shell script syntax** - Validates shell scripts with `bash -n`
+- ✅ **JavaScript syntax** - Validates JS files with `node --check`
+- ✅ **Mintlify config** - Validates docs.json/mint.json syntax
+- ✅ **Import paths** - Ensures snippets imports use absolute paths
+- ✅ **Browser validation** - Tests MDX files in headless browser (requires `mint dev` running)
+
+## Installation
+
+To install the pre-commit hook:
+
+```bash
+cp .githooks/pre-commit .git/hooks/pre-commit
+chmod +x .git/hooks/pre-commit
+```
+
+Or use the install script:
+
+```bash
+./.githooks/install.sh
+```
+
+## Manual Installation
+
+If the install script doesn't work:
+
+```bash
+# Copy the hook
+cp .githooks/pre-commit .git/hooks/pre-commit
+
+# Make it executable
+chmod +x .git/hooks/pre-commit
+
+# Verify it's installed
+ls -la .git/hooks/pre-commit
+```
+
+## Testing
+
+Test the hook by staging a file with a violation:
+
+```bash
+# Create a test file with ThemeData (should fail)
+echo 'import { ThemeData } from "/snippets/styles/themeStyles.jsx";' > test-violation.jsx
+git add test-violation.jsx
+git commit -m "test"  # Should be blocked
+
+# Clean up
+rm test-violation.jsx
+git reset HEAD test-violation.jsx
+```
+
+## Bypassing (Not Recommended)
+
+If you absolutely must bypass the hook (not recommended):
+
+```bash
+git commit --no-verify -m "message"
+```
+
+**Warning:** Only bypass if you have a legitimate reason and understand the style guide violations.
+
+## Style Guide Reference
+
+See: `v2/pages/07_resources/documentation-guide/style-guide.mdx`

.githooks/install.sh

@@ -0,0 +1,32 @@
+#!/bin/bash
+# Install git hooks
+
+HOOKS_DIR=".git/hooks"
+SOURCE_DIR=".githooks"
+
+if [ ! -d "$HOOKS_DIR" ]; then
+    echo "Error: .git/hooks directory not found. Are you in the repository root?"
+    exit 1
+fi
+
+if [ ! -d "$SOURCE_DIR" ]; then
+    echo "Error: .githooks directory not found. Are you in the repository root?"
+    exit 1
+fi
+
+echo "Installing git hooks..."
+
+# Install pre-commit hook
+if [ -f "$SOURCE_DIR/pre-commit" ]; then
+    cp "$SOURCE_DIR/pre-commit" "$HOOKS_DIR/pre-commit"
+    chmod +x "$HOOKS_DIR/pre-commit"
+    echo "✓ Installed pre-commit hook"
+else
+    echo "✗ pre-commit hook not found in $SOURCE_DIR"
+fi
+
+echo ""
+echo "Git hooks installed successfully!"
+echo ""
+echo "The pre-commit hook will now check for style guide violations."
+echo "See .githooks/README.md for details."