feat: migrate documentation site to OINK 1.0

[imbajin]

Test drive

Open the live ASF staging site →

Experience	Try it
Refined homepage	English · 中文
Task-oriented Docs	Open latest Docs and hover Documentation to switch versions
Local search	Open Docs and press / or ⌘K
Supported versions	1.7 · 1.5
Chinese archives	1.7 中文 · 1.5 中文
Community	English · 中文

The preview uses the same version manifest, build matrix, validation, and publication path intended for master.

Why this migration

This PR moves the Apache HugeGraph documentation site from Docsy to pinned OINK 1.0.

It preserves the familiar HugeGraph product story and public URLs while improving how users navigate, search, and compare documentation across languages and supported versions.

Visual evolution: A → B → C

A — Docsy baseline	B — Initial OINK layout	C — Refined OINK homepage
Original product copy in the Docsy shell.	OINK functionality with a visually separate header.	Familiar content with an integrated header, task-oriented Docs, and a simpler footer.

The append-only visual history and alternatives remain available in #467.

What improves

• task-oriented Docs navigation with Get Started, Components, and Develop open by default;
• one concise HugeGraph lockup across visible shell surfaces while page titles and metadata remain Apache HugeGraph;
• one continuous purple Docs header across the navbar and sidebar, implemented with OINK structure and theme tokens;
• edge-aligned Homepage and Community navigation plus a sticky Homepage header;
• fast bilingual local search with keyboard access;
• desktop/mobile language and version navigation for latest, 1.7, and 1.5;
• responsive reading, dark mode, print support, accessible controls, and no-JavaScript fallbacks;
• preserved /docs/..., /cn/docs/..., blog, download, and /client-go/ routes;
• restored bilingual Community content, with a contributor showcase tracked separately in Add a contributor showcase to the Community page #468.

Main changes

• pins OINK 1.0, Hugo Extended 0.165, and Go 1.27;
• migrates Docsy-specific landing and shell behavior to data-driven OINK layouts;
• preserves the original Homepage title, descriptions, calls to action, and core illustration;
• restores legacy Homepage body typography, blue links, and the yellow Download action;
• drives sidebar, pager, Docs cards, active paths, and navigation data from one bilingual task-oriented IA;
• configures default expansion through bilingual OINK page parameters rather than title checks;
• shares one display-brand configuration across navbar, sidebar, and subnav;
• renders supported versions from an explicit manifest without modifying release branches;
• isolates language, version, canonical, search, sitemap, action, asset, and error-page output;
• publishes through the dedicated ASF OINK staging site without replacing standard staging or production.

flowchart LR
  A[Version manifest] --> B[Latest, 1.7, and 1.5]
  B --> C[English and Chinese builds]
  C --> D[Validate and aggregate]
  D --> E[ASF staging]
  D --> F[Production publication]

Loading

Mobile preview

Navigation and footer refinement

Documentation versions	Compact ASF footer

Homepage mobile drawer	Docs mobile drawer

Unified Docs brand header

Verification

• strict production and staging builds cover latest, 1.7, and 1.5;
• 66 unit/integration tests, Ruff, source-link checks, and generated-output validators pass locally;
• canonical, hreflang, sitemap, navigation, search, assets, redirects, and error documents are validated per language/version;
• desktop/mobile, light/dark, sidebar expand/collapse, keyboard behavior, 200% zoom, forced colors, print, and no-JavaScript readability are browser-tested;
• staged resources, CSP, MIME types, fragments, protected paths, and case-sensitive historical routes are verified before publication.

Current exact-head CI details remain available from the pull request checks.

Rollback and exclusions

The migration can be reverted through the repository's normal pull-request revert flow; it does not require rewriting published branch history. Neither standard asf-staging nor asf-site is used by this preview.

This PR intentionally does not redesign the future contributor gallery, mechanically rewrite unrelated historical content, define a new EOL-wide SEO policy, or add an API renderer without a reliable OpenAPI source.