The site contains both editorial articles and pages generated from structured data. The production and review process differs by page type.
Data sources by page type
- Pokédex, species, type, and interactive tool pages: cached PokeAPI records, supplemented by locally maintained game-availability rules.
- Walkthrough pages: structured encounter, trainer, item, event, and map records. Depending on the game, these come from public game-source projects, PokeAPI exports, and named reference pages such as Bulbapedia. The exact mix varies by walkthrough series.
- VGC data pages: locally cached tournament standings and team records from PokéData, with official event pages and specialist tournament sites used as supplementary references.
- Guides and rankings: editorial articles. Relevant rules, tournament information, and external references are linked within the article where applicable.
Specific providers and repositories are listed on the Sources page.
How generated pages are built
Maintenance scripts fetch or read source records, normalize them into local JSON and other structured datasets, and preserve source metadata where available. Site templates then turn those records into static tables, lists, and page text during the Astro build. The public page does not depend on a live third-party API request at visit time.
Pages also emit route-specific structured metadata, including breadcrumb and WebPage or Article JSON-LD. That metadata is derived from the page title, description, route, and known content attributes rather than used as a substitute for visible content.
Human review
Editorial articles are reviewed as individual pages. For generated pages, review occurs primarily at the source-mapping, dataset, and template level, supported by build checks, validation reports, coverage counts, and samples of rendered output. We do not claim that every generated row has been manually checked one by one.
When a systematic error is confirmed, the preferred correction is made in the source data, mapping, or generator so every affected page can be rebuilt consistently.
Reporting an error
Email [email protected] with the page URL, the game and version, the incorrect field or statement, the expected value, and a supporting source if available. Reports are checked against the source used by the page before a correction is published.
Known limits
Local datasets are snapshots and can lag a source update. Sources may also disagree or omit a field. When the available evidence is incomplete, the site should omit the claim or label the gap instead of presenting an unsupported value as certain.