equislinux/web is the public documentation portal of the X Linux project:

• Landing — hero with the ISO download, screenshot showcase (public/showcase/), a "Why X" feature grid, install steps, the repository grid, the two packaging paths (pacman [x] and native .xp for xpm) and a docs call to action.
• Docs — every repository of the organization documented in a browsable sidebar, rendered from markdown, with a language switch (English/Spanish).

The documentation sources live in equislinux/wiki and are copied into content/<lang>/<section>/. Each page links back to its source on GitHub.

• Next.js 16 (App Router) with fully static export.
• Tailwind CSS 4 with a monochrome design system (black/gray in light, white/gray in dark) and a light/dark toggle.
• Geist Sans and Mono via next/font.
• react-markdown + remark-gfm for the docs.

app/
  page.tsx                    # English landing at the root
  [lang]/page.tsx             # /en and /es landings
  [lang]/docs/page.tsx        # docs home (overview + section cards)
  [lang]/docs/[...slug]/      # one route for every docs page
components/                   # Navbar, Footer, Hero, Downloads, Showcase,
                              # Features, Install, RepoGrid, DocsShell, Markdown
content/
  en/<section>/<page>.md      # documentation sources (English)
  es/<section>/<page>.md      # documentation sources (Spanish)
lib/
  docs.ts                     # sections manifest + markdown loaders
  i18n.ts                     # UI strings (en/es)
  site.ts                     # repository list

npm install
npm run dev      # http://localhost:3000/web
npm run build    # static export in ./out

The site uses basePath: /web (GitHub Pages project path), so both the dev server and the exported assets live under /web.

The layout is checked free of horizontal overflow at 390/360/320 px (grids use minmax(0, 1fr) tracks, prose wraps long tokens and body clamps with overflow-x: clip as a safety net).

1. Add the markdown under content/en/<section>/ and content/es/<section>/.
2. Register the file in SECTIONS in lib/docs.ts.
3. Push to main: the deploy workflow builds and publishes to GitHub Pages.