Files
gridpilot.gg/docs/CONTENT.md
2025-12-31 15:39:28 +01:00

169 lines
4.0 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Content Concept: Guides & Docs
Goal
Build organic traffic, trust, and authority without advertising, primarily for league admins, secondarily for drivers, stewards, broadcasters, and sponsors. Content should:
• solve real problems
• be useful even without our platform
• implicitly prove deep domain understanding
No marketing fluff. No feature pitching. Utility first.
Content Pillars
1. League Operations (Core)
Audience: League Admins
Topics:
• Season planning: formats, calendars, breaks
• Driver management at scale (signups, reserves, no-shows)
• Points systems that dont explode mid-season
• Handling protests without burning out
• Promotion / relegation models that actually work
• Dealing with dropouts mid-season
• Multi-class league pitfalls
• Fair penalty escalation over a season
Example Articles:
• “How Most Leagues Break in Week 4”
• “Designing a Season That Survives Real Life”
• “Why Your Penalty System Feels Unfair (And What To Do Instead)”
2. Stewarding & Fairness
Audience: Stewards, Admins
Topics:
• What makes a good steward (and what doesnt)
• Consistency vs. speed in decision making
• Evidence handling: replays, POVs, timestamps
• Protest workflows that scale beyond 20 drivers
• Community voting vs. steward authority
• Preventing steward burnout
Example Articles:
• “Stewarding Is a Job, Not a Favor”
• “Why Protests Feel Like Court Cases”
• “Consistency Beats Perfection in Stewarding”
3. Sponsoring & Prize Money (Very Differentiating)
Audience: League Admins, Sponsors
Topics:
• Why most league sponsorships fail
• Trust problems around prize money
• Transparent prize distribution models
• Fixed vs. performance-based payouts
• Season-long vs. per-race sponsorships
• Escrow concepts explained simply
Example Articles:
• “Why Sponsors Dont Trust League Racing”
• “Prize Money Without Drama”
• “What Sponsors Actually Care About (Spoiler: Not Your Logo Size)”
4. Drivers & Identity
Audience: Drivers
Topics:
• Why driver identity matters in leagues
• Smurfing, alt accounts, and trust erosion
• Reputation systems: what works, what doesnt
• Stats that actually mean something
• Why drivers ghost leagues
Example Articles:
• “Why Drivers Disappear Mid-Season”
• “Reputation Is the Real Rating”
5. Broadcasting & Streaming
Audience: Broadcasters, Streamers, Admins
Topics:
• What makes a league stream watchable
• Broadcaster reliability problems
• Paying broadcasters fairly
• Minimum viable production setups
• Stream verification and accountability
Example Articles:
• “Why Most League Streams Die After Two Races”
• “Streaming Is Infrastructure, Not Marketing”
6. Game-Agnostic Racing Concepts
Audience: Cross-sim leagues
Topics:
• What every racing sim gets wrong about leagues
• Why matchmaking doesnt replace leagues
• Differences between casual events and real championships
• Why league tooling will never be built into sims
Example Articles:
• “Why Sims Will Never Build Proper League Tools”
• “Matchmaking Is Not Competition”
Docs vs. Guides
Docs (Reference)
• Definitions (Season, Championship, Session, Stint, Protest, etc.)
• League structure glossary
• Stewarding terminology
• Sponsorship terminology
Purpose: clarity, shared language, authority.
Guides (Opinionated)
• Step-by-step reasoning
• Tradeoffs explained
• Based on real-world league pain
Purpose: insight, trust, positioning.
Format Rules
• Short paragraphs
• Clear headings
• Concrete examples
• No calls to action at the end
• No signup pressure
If someone reaches the end and thinks:
“Whoever wrote this actually gets it.”
— it worked.
Long-Term Payoff
This content becomes:
• SEO moat
• onboarding material
• shared links inside Discords
• justification for admins to switch
It answers questions before people know they need a platform.