Documentation Maintenance

KTransformers docs should be task-first and support-status aware.

Canonical Structure

Use this sidebar structure for public docs:

1. Get Started
2. Inference
3. Fine-Tuning
4. Advanced Features
5. Supported Models
6. Technical Work
7. Hardware Platforms
8. Developer Guide
9. Command Reference

Update Rules

• Keep public entry points centered on kt-kernel + sglang-kt for inference.
• Keep public SFT entry points centered on ktransformers[sft] + LLaMA-Factory.
• Keep task guides and technical background separate. Put runnable user flows under Inference or Fine-Tuning; put talks, architecture notes, and migration notes under Technical Work.
• Put model claims through the support matrix.
• Keep legacy pages out of primary navigation unless they are rewritten.
• Avoid writing generic support claims when the result is model-specific.

Link Rules

Internal Markdown links should use /docs/.... The site router adds the locale prefix automatically.

Use:

[Support Matrix](/docs/support-matrix)

Do not use:

Hard-coded locale-prefixed docs links such as /en/docs/support-matrix.