Every story on gamer11 follows the same editorial standard. The lead carries the verified event — who, what, when, where and why it matters — within the first two paragraphs. The body adds context the lead cannot fit. The closing points at the next event to watch, not at a recap of what just happened. Stories cite the source they were drawn from; quotes come from the verified source and are not paraphrased. Match recaps cite the league's bracket page and the verified broadcast. Roster moves cite the org's official announcement and the verified handle. Patch impact cites the developer's official patch post. Watch guides cite the broadcast partner's schedule. Every figure carries a verification note attached to the entry. Where a figure is pending publication by the league, the story says so explicitly and does not invent one. We do not fabricate placement, roster composition, dates, scores, brackets or player data. We do not run rumors. We do not paraphrase quotes. We do not auto-generate editorial copy without a human in the loop.
Every story on gamer11 follows the same editorial standard. The lead carries the verified event — who, what, when, where and why it matters — within the first two paragraphs. The body adds context the lead cannot fit. The closing points at the next event to watch, not at a recap of what just happened. Stories cite the source they were drawn from; quotes come from the verified source and are not paraphrased. Match recaps cite the league's bracket page and the verified broadcast. Roster moves cite the org's official announcement and the verified handle. Patch impact cites the developer's official patch post. Watch guides cite the broadcast partner's schedule. Every figure carries a verification note attached to the entry. Where a figure is pending publication by the league, the story says so explicitly and does not invent one. We do not fabricate placement, roster composition, dates, scores, brackets or player data. We do not run rumors. We do not paraphrase quotes. We do not auto-generate editorial copy without a human in the loop.
The editorial standard applies across the site. The verification note attached to each entry lists the source page the data was drawn from. We do not fabricate placement, roster composition, dates, scores, brackets or player data. Where a figure is pending publication by the league, the entry says so explicitly and does not invent one.
For viewers who want to read more, the related hubs linked below cover the same topic from different angles. The tournament index pairs with the match schedule to surface the format primer for each event. The team directory pairs with the player profiles to surface the current roster for each team. The news desk pairs with the guides to surface the editorial standard for each story.
Every figure on the site links back to a verified source: the league page, the org's official announcement, or the developer's patch post. Where a figure is pending publication, the entry says so.
Every story passes through the same three-step flow before publication. The flow is editorial discipline, not a checklist. The flow exists to protect the reader from invented figures and the desk from publishing unverified copy.
The desk reads the underlying source page — the league bracket, the org's announcement, the developer's patch post, the verified broadcast partner's channel — and confirms the figure is published. If the source is inaccessible, title-only, or unrelated to the assigned hub, the desk stops with SOURCE_UNUSABLE before any writing begins.
The desk compares the figure to the source. If the source carries a specific figure, the desk uses that figure verbatim. If the source carries a partial figure, the desk says so explicitly and marks the entry as pending. The desk does not infer figures from a single match or from a partial source.
Before publication, a second editor reviews the story for filler, duplicated ideas, unsupported certainty, fabricated details, monotonous sentence patterns, awkward transitions, promotional language and every remaining AI cliché. The second editor confirms that the headline matches the story, the lead reaches the event immediately, quotations and numbers are sourced, keywords read naturally, and the ending adds new value.
Every figure on the site follows the same sourcing ladder. The ladder is a hierarchy, not a preference list. The desk uses the highest-rung source available for each figure. Where the highest-rung source is unavailable, the desk drops to the next rung and marks the entry accordingly. The desk never uses a lower rung when a higher rung is available.
The top rung is the league's published bracket page. The bracket page carries the round layout, the seedings, the start times and the verified broadcast links. Where the bracket page carries a figure, the desk cites the bracket page verbatim. The second rung is the org's official announcement. The announcement carries roster moves, contract length and the verified handle. Where the announcement carries a figure, the desk cites the announcement verbatim.
The third rung is the developer's official patch post. The patch post carries the patch version, the agent changes, the map changes, the economy changes and the side selection changes. Where the patch post carries a figure, the desk cites the patch post verbatim. The fourth rung is the verified broadcast partner's channel. The channel carries the verified broadcast links and the caster desk lineup. Where the channel carries a figure, the desk cites the channel verbatim.
The fifth rung is the public social post from a verified handle. The desk uses the public social post only when the higher rungs are unavailable. The sixth rung is the Wikipedia article. The desk uses the Wikipedia article only when the higher rungs are unavailable, and only for reference-led explainers. The desk never uses rumor, anonymous sources, or paraphrased quotes.
The desk also publishes a verification note on every entry that cites a third-party source. The verification note lists the source page the data was drawn from and the date the desk confirmed the figure. Where the figure is pending publication by the league, the entry says so explicitly. The verification note is part of the editorial standard.
Five references on the site for viewers who want to read the editorial standard, the verification flow and the source ladder in detail.
The site is an editorial newsroom covering the competitive gaming circuit. The about page describes the editorial scope, the verification flow and the responsible-coverage framework.
Editorial coverage of competitive gaming, not wagering advice. Age, jurisdiction, source-evidence standards and the responsible-coverage framework applied to every story.
How to reach the editorial desk for corrections, clarifications, source submissions and story leads. The desk reads every message; corrections and clarifications get the fastest response.
Match recaps, roster moves, patch impact and watch guides. Editorial copy that cites the source, not speculation.
How to read a patch post. Agent changes, map changes, economy changes and side selection, in plain language with a worked example from patch 8.4.
The editorial desk covers methodology the same way it covers every other editorial subject: cite the source, do not invent figures, and mark pending entries explicitly. The desk reads the league's published documentation after every cycle close and updates the methodology on the guides index page. The desk does not infer methodology entries from a single broadcast; the entry must reflect the league's published documentation across the cycle.
The methodology page documents the verification flow applied to every story. The flow is editorial discipline, not a checklist. The flow exists to protect the reader from invented figures and the desk from publishing unverified copy. The flow covers the source check, the fact check and the editorial review. Each step has a defined outcome.
The methodology page documents the sourcing ladder applied to every figure. The ladder is a hierarchy, not a preference list. The desk uses the highest-rung source available for each figure. Where the highest-rung source is unavailable, the desk drops to the next rung and marks the entry accordingly. The desk never uses a lower rung when a higher rung is available.
The methodology page documents the editorial standard applied to every article. The standard covers the lead, the body and the closing. The lead carries the verified event within the first two paragraphs. The body adds context the lead cannot fit. The closing points at the next event to watch, not at a recap of what just happened.
The methodology page documents the response time applied to every message. Corrections and clarifications get the fastest response; the desk publishes within 24 hours during business days. Story leads and source submissions get a response within 48 hours during business days. Sponsorship inquiries get a response within one week.
The methodology page documents the verification note applied to every entry that cites a third-party source. The verification note lists the source page the data was drawn from and the date the desk confirmed the figure. Where a figure is pending publication by the league, the entry says so explicitly. The verification note is part of the editorial standard.