Editorial Policy

1. Purpose

The editorial goal is to make Cobblemon Mod setup and maintenance easier to understand without pretending that one configuration applies to every player. Content should separate stable principles—such as backups, clean profiles and version matching—from details that may change as Minecraft, loaders, add-ons and Cobblemon Mod evolve.

2. Source priority

Technical claims should be checked against current upstream project information whenever practical. Project documentation, changelogs, release notes and reproducible in-game behavior are preferred over copied summaries. Community discussions can be useful for identifying recurring problems, but they should not silently replace documented requirements when a more direct source is available.

3. Version context

An article should make clear when instructions depend on a specific Minecraft version, loader or Cobblemon Mod version. Editors should avoid presenting “latest” as a permanent fact. If a version number is important, the article should state the relevant context or direct readers to the homepage Versions and Compatibility sections for an additional check.

4. Download-link policy

The site uses one direct software download button in the homepage hero. That link should remain clearly labeled, use nofollow, and should not be configured to force a new browser tab. Additional software download buttons should not be added elsewhere unless the project requirements are deliberately changed. Guide pages should focus on instructions rather than duplicating download destinations.

5. Guide structure

Long-form guides should explain the reason behind important steps rather than publishing only a short checklist. Installation, update and troubleshooting articles should emphasize clean profiles, exact version records, backups, controlled tests and small changes. A guide should help the reader isolate a problem instead of encouraging random file replacement.

6. Corrections

When an error is discovered, the preferred response is to correct the page and review related pages that may repeat the same assumption. Broken internal links, incorrect route names, outdated version references and responsive layout issues are editorial quality problems as well as technical problems. Corrections should preserve useful URLs where possible and should not introduce duplicate content pages unnecessarily.

7. Independent status and naming

The website should not imply official affiliation with Cobblemon Mod, Minecraft, Pokémon or any unrelated hosting provider. Names are used to identify the subjects discussed. Editorial copy should distinguish this independent guide project from official projects, maintainers and third-party community work.

8. Safety and data protection

Articles that involve updates, worlds or servers should include backup guidance when data loss is a realistic risk. Instructions should not recommend deleting the only copy of a working profile or save. Troubleshooting should begin with logs, compatibility checks and recent changes before destructive actions are suggested.

9. External projects

Third-party or community projects should be described according to what can be verified from their own published information. The site should not imply that every Cobblemon-related add-on is maintained by the same team or is compatible with every version. Compatibility and maintenance status can change, so readers should be encouraged to confirm requirements for the exact environment they use.

10. Review cycle and responsive quality

High-change information—especially versions, compatibility and update guidance—should be reviewed when upstream changes occur. Editorial review also includes practical layout checks: headings must wrap without clipping, cards must not force horizontal scrolling, images should scale inside their containers, navigation must remain accessible, and the footer must not overlap or overflow the viewport.

11. Content depth and reader-first standard

Length alone is not a quality target, but legal and policy pages should contain complete, substantive sections rather than placeholder copy. Long guides should be detailed when the task requires detail, while homepage sections should remain scannable. The final test is whether the page helps a reader make a safer and better-informed setup decision using clear navigation, accurate labels and transparent uncertainty.

12. Consistency across the site

Navigation labels, compatibility wording and download behavior should remain consistent across templates. When a topic has been consolidated into the homepage, editors should link to the relevant homepage section instead of recreating a separate content page. Guide articles may remain separate because they provide long-form instruction, but they should return readers to the shared category and homepage structure.