Guide

Editorial Policy

Poly Track is moving away from being a passive directory of map codes. The editorial layer exists to explain what a track teaches, who it helps, and why it deserves a full review. We only publish featured coverage when the page gives players practical context they can use before loading the map.

What We Include

We feature tracks that have a completed editorial review, useful original guidance, and enough practical detail that a player can learn something before loading the map. We also keep some archive material accessible so players can still browse and play maps while deeper notes are prepared.

  • Published editorial review
  • Enough original guidance to explain why the track matters
  • Clear creator attribution when available

What We Do Not Feature

We do not feature tracks solely because they exist or because they have a valid code. Placeholder reviews and maps with incomplete editorial notes can remain accessible, but they do not receive featured placement until the page explains the route, the driving lesson, and the right kind of player for the map.

  • Placeholder copy or unfinished review blocks
  • Maps with no meaningful editorial explanation
  • Pages that do not yet explain a useful player lesson

Corrections, Downgrades, and Removals

Editorial coverage can be revised when better creator attribution appears, when a track stops loading correctly, or when an older review no longer helps players make a good choice. A page can also lose featured status while remaining playable.

  • We correct factual mistakes when they are verified.
  • We can remove advertising from pages that need more complete review notes.
  • We can downgrade or remove featured status when a better editorial standard is needed.

How Archive Material Differs From Reviews

Some community maps are useful as archive entries before they are ready for a full recommendation. Archive material helps players preserve and locate map codes, while reviewed pages explain why a route is worth practicing and what a player should expect from it.

This separation protects readers from confusing a basic listing with a finished recommendation. When a page earns full review treatment, it should add original judgment, route-specific notes, and a clear reason to choose that map over another option.

  • Archive entries help preserve community map access.
  • Reviewed pages explain practice value and route behavior.
  • Featured recommendations require enough context to guide player choice.