[both projects] Migrate docs to Fumadocs Static Export (GitHub Pages compatible)

[strausmann]

Summary

Both documentation projects (crowdsec-manager and middleware-manager) currently run in Next.js SSR mode and use server-side API routes that are incompatible with static export. Migrating to output: 'export' would enable GitHub Pages hosting and eliminate the need for a Node.js runtime server.

Source

• Gap analysis: docs/upstream-contributions/crowdsec-manager/docs-analyse.md (Sections 5.1–5.3)
• Gap analysis: docs/upstream-contributions/middleware-manager/docs-analyse.md (Section 5)

Current State (Both Projects)

// next.config.mjs — current state
const config = {
  reactStrictMode: true,
};

No output: 'export' — currently deployed via Vercel or similar SSR host.

What Blocks Static Export

Component	Both Projects	Required Change
app/api/search/route.ts	Yes	Replace with fumadocs-core static search
app/llms-full.txt/route.ts	Yes	Generate as static file at build time
app/og/docs/[...slug]/route.tsx	Yes	Remove or pre-render as static images
sitemap.ts	crowdsec-manager	Convert to static sitemap.xml
robots.ts	crowdsec-manager	Convert to static robots.txt

Required Changes per Project

crowdsec-manager docs

1. Add output: 'export' to next.config.mjs
2. Replace search API route with fumadocs static search (fumadocs-core SearchDialog with static index)
3. Migrate sitemap.ts → static sitemap.xml
4. Migrate robots.ts → static robots.txt
5. Handle or remove OG image generation route
6. Handle or remove llms-full.txt route
7. Add export script to package.json
8. Validate: next build produces a fully static out/ directory

middleware-manager docs

1. Add output: 'export' to next.config.mjs
2. Replace search API route with fumadocs static search
3. Handle or remove OG image generation route
4. Handle or remove llms-full.txt route
5. Add export script to package.json
6. Validate: next build produces a fully static out/ directory

fumadocs Static Search Migration

Fumadocs officially supports static export. The search migration involves:

• Removing the server-side app/api/search/route.ts
• Building a static search index at build time
• Using fumadocs-core's client-side search dialog

Reference: https://fumadocs.vercel.app/docs/headless/search/static

Acceptance Criteria

• output: 'export' added to next.config.mjs in both projects
• next build completes without errors in both projects (produces out/ directory)
• Search works in the static build (client-side, no server required)
• All MDX pages render correctly in the static build
• package.json has an export or build:static script
• CI pipeline (GitHub Actions) validates the static build

Dependencies

This issue should be tackled after Phase 1 content corrections are complete in both projects, to avoid re-running the build validation multiple times.

• Depends on: Issues [crowdsec-manager] Fix incorrect API docs and outdated architecture information #1, [crowdsec-manager] Complete environment variables documentation (9 of 40+ documented) #2, [crowdsec-manager] Document Hub Browser feature (8 nav entries, 12 API endpoints, zero docs) #3, [crowdsec-manager] Document History, Config Validation/Drift Detection, and Simulation Mode #4, [crowdsec-manager] Add Pangolin deployment guide (docker-compose.pangolin.yml undocumented) #5 (crowdsec-manager Phase 1)
• Depends on: Issues [middleware-manager] Fix incorrect and outdated content across multiple pages #6, [middleware-manager] Document Security Hub: TLS Hardening and Secure Headers (completely missing) #7, [middleware-manager] Document External Middlewares feature (Traefik-native middleware assignment) #8, [middleware-manager] Document ENABLE_FILE_CONFIG mode and complete missing env-vars #9 (middleware-manager Phase 1)

Effort Estimate

L (4–6 hours across both projects, including validation)

[github-actions]

This issue has been inactive for 14 days. If it's blocked by #14 (Maintainer Alignment), please add status:blocked label. If work can proceed, please update the status.