Website repository
EvoMap/evomap-website owns public EvoMap and EvoX product pages, documentation, download-manifest consumption, and frontend experience. It presents released facts but does not generate upstream binaries.
Primary responsibilities
- Product and feature pages, EvoX documentation, and localized content.
- Download entry points, channels, and presentation of public release manifests.
- Routing, search, SEO, Markdown rendering, and responsive frontend behavior.
- Page-level link, asset, desktop, and mobile visual acceptance.
Factual sources for content
Use this order when authoring documentation:
- Current product source, formal release manifests, and package metadata.
- Maintained specifications, READMEs, and runbooks in the owning repository.
- Real product UI, command help, and reproducible observation.
- Mocks, plans, and similar products may guide structure but do not prove EvoX support.
Documentation workflow
- Update Chinese and English pages together with navigation metadata.
- Check internal links, headings, and one-to-one page coverage.
- Run relevant structural tests and the production build.
- Inspect navigation, content, tables, code blocks, and assets at desktop and mobile viewports.
- Mark unconfirmed content explicitly instead of deleting an entire page to hide a knowledge gap.
Release boundary
The website may present a Desktop download manifest, but it cannot build, sign, release, or verify installers on behalf of Desktop or core repositories. When an asset is absent from the manifest, show a real unavailable state instead of synthesizing a download link.
Related pages
EvoX Docs · Developers · Repository boundaries