Documentation sources and maintenance
Understand the version boundary and keep these guides accurate.
SkinsRestorer 15.12.6All platformsReviewed
These pages target SkinsRestorer 15.12.6, reviewed on October 1, 2026. Website workflows describe this repository's upload and generator implementations.
Source of truth
| Subject | Primary source |
|---|---|
| Configuration keys and defaults | Release configuration classes |
| Commands and permissions | Release command definitions |
| API signatures and exceptions | Release public API |
| Fabric requirements | Release metadata |
| Velocity forwarding | PaperMC instructions |
| DiscordSRV avatar configuration | DiscordSRV reference |
| MineSkin limits and grants | MineSkin documentation |
Do not replace release facts with an unreviewed development branch. External platform configuration and service limits need their own version check.
Documentation design
The structure separates guided learning, task procedures, exact reference, and explanations. It follows Diátaxis and uses Fumadocs for navigation, code blocks, and search.
A procedure needs prerequisites, working steps, an expected result, and a useful failure branch. Reference tables need exact names and a source version.
Contribute a correction
Use the page's GitHub link to edit its MDX source. Include the affected release and a reproducible reason for a technical correction.
For a broken step, state what you tried and the actual result. For a new feature, add the procedure and reference together.
Release checklist
Maintainers can find the source inventory and local validation instructions in the repository's documentation/README.md.
For each release, compare source declarations, update the inventory and affected pages, compile the complete Java example, and build the website. Then inspect representative installation, upload, proxy, and API pages.
Treat page feedback as a correction queue. Record the URL, release, reported result, and resolution in an issue or documentation change.
Did this page help?
Last updated on