Resource
Mapping the public Qwen surface into a deployable site
A short editorial note on how the README-only input becomes mirrored docs routes, discovery assets, and runtime-loaded resources.
2026-03-174 min read
Available locales
Why this site exists
The local source input for this project is a single upstream README, not an application codebase. The public website therefore has to reconstruct the information architecture from documentation rather than inherit a runnable product.
That is why the web layer separates stable source-backed product data from editorial content that can evolve independently.
What gets mirrored
The bilingual route map covers install, models, benchmarks, demos, API, tool use, long context, FAQ, and license.
- Parallel `/en` and `/zh` routes
- Metadata alternates and crawlable discovery assets
- Runtime resource loading via `QWEN_CONTENT_DIR`
Source anchors