5
Published entries
The listing is grouped by published translation keys, not by raw source files.
Community-run docs surface, derived from public Qwen source materials and not presented as the primary upstream home by default.
Resources
Editorial entries are loaded at runtime when `QWEN_CONTENT_DIR` is provided, with local fallback content for development and preview.
5
The listing is grouped by published translation keys, not by raw source files.
5/5
Entries that already have both English and Chinese variants published.
0
Cards stay visible when only one locale is published, with an explicit translation status.
Time-bound updates and editorial notes that track public changes in the historical Qwen surface.
Seed content proving the shared editorial contract for the standalone site.
Operational notes, API decisions, deployment references, and hub links that stay useful over time.
A short editorial note on how the README-only input becomes mirrored docs routes, discovery assets, and runtime-loaded resources.
A seeded resource describing how the deployed app reads shared content.
A practical note on why `robots.txt`, `sitemap.xml`, `feed.xml`, and `llms.txt` belong to the product surface for an AI-oriented docs site.
Longer-form writeups that can be cited, translated, and updated independently from the app bundle.
Sample article showing the intended editorial workflow for runtime content.