Quick answers before detail
Guide pages should answer the main player question near the top, then support it with tables, checklists, related pages, and caveats.
Editorial policy
Gale Atlas is built around practical player help. The site can use planning frameworks and placeholder tables during launch, but exact game claims should be clearly labeled until they are checked against the current Windrose build.
Guide pages should answer the main player question near the top, then support it with tables, checklists, related pages, and caveats.
Exact locations, material costs, unlocks, recipes, boss drops, and route claims should stay marked as needing verification until checked in the current build.
Pages use visible update dates and verification notes so players can judge whether a guide is safe to trust after patches.
Guide images should be original Gale Atlas illustrations or current-build screenshots. Generated illustrations must be labeled and should not look like official Windrose key art.
Videos should come from official or clearly public sources, with the source name and checked date shown beside the video link or embed.
Player corrections should include the guide URL, game version if known, and the exact value or route that needs review.
Editorial workflow
Gale Atlas can publish useful planning help before every exact Windrose value is final, but the page must show readers which parts are practical guidance, which parts are current-build checked, and which parts still need review.
Each page starts from a real search problem, such as server visibility, save files, beginner routes, settings, or material planning. The first screen should help the player decide what to try next.
Ports, commands, file paths, coordinates, recipes, damage thresholds, and patch-sensitive values stay caveated until the current Windrose build supports them.
Original Gale Atlas art, generated illustrations, screenshots, public trailers, and third-party videos should be labeled in plain language near the page where they appear.
When a page gains a checked route, a corrected value, a new source label, or a major structure change, the update log should explain what changed and what still needs review.
This ladder decides whether a guide can present a claim as a final answer, a careful suggestion, or a review-needed note.
Troubleshooting order, planning questions, and beginner checklists can publish when they avoid exact unverified values.
Exact game claims should be promoted only after they are checked against the current Windrose build, source label, or public store information.
Exact ports, commands, file paths, coordinates, prices, material costs, boss drops, and route timing stay labeled as review-needed.
Conflicting player reports, stale screenshots, broken embeds, missing source labels, or outdated patch-sensitive values should trigger a visible correction path.
A useful correction names the page, the current game version if known, what changed, and how the player reproduced it. Corrections that affect exact values should be reflected in the guide, the review status page, or the public update log.
Send a correctionEvery new guide can include original visual material, but readers should always know what was generated by Gale Atlas and what came from an external video source.
Trust links