2Ia Org Content Expansion Research Report - Source Excerpt 05 - Roadmap, competitor comparison, and risk matrix

Back to 2Ia Org Content Expansion Research Report

Summary

This source excerpt begins near Roadmap, competitor comparison, and risk matrix and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-16-publication-system-followup/2IA.org Content Expansion Research Report.md.

**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-16-publication-system-followup/2IA.org Content Expansion Research Report.md

The voice should become more direct than it is now, but it should not become dumber. The right benchmark is a hybrid: keep 2IA’s existing “sharp without becoming reckless” framing, borrow some of Fight for the Future’s willingness to be blunt, and avoid copying the maximalist pitch of sites that substitute heat for structure. Fight for the Future’s own 2026 strategy page openly says it will not “tone down” its messaging, and its 2024 page shows how an advocacy organization can be strong, candid, and combative while still giving readers campaign evidence, priorities, and asks. That said, 2IA should use this style **only when it can back the language with evidence**. citeturn3view1turn18view0turn18view1

A good 2IA voice guide would read like this:

| Voice principle | Do | Avoid |
|---|---|---|
| Direct | “This policy expands surveillance with weak oversight.” | “Concerns have been raised regarding…” |
| Adult | Assume the reader can handle complexity and conflict | Civics-class baby talk or sterile NGO euphemism |
| Evidence-led | State the claim, show the evidence, mark uncertainty | Vibes, innuendo, or rhetorical fog |
| Rights-forward | Speak clearly about speech, privacy, due process, and public accountability | Flattening everything into generic “safety” language |
| Controlled edge | One sharp sentence can carry an argument | Empty swagger, pseudo-intelligence cosplay, or indulgent profanity |
| Lawful | Defend rights; do not teach abuse | Threats, doxxing, evasion advice, sabotage fantasy, or incitement |

That voice has to be enforced by templates. I recommend the following content template set.

| Content type | Target length | Required blocks |
|---|---:|---|
| Issue hub | 1,800–2,400 | What this issue is; why it matters; common myths; key debates; featured reading; glossary; CTA |
| Investigation | 2,200–3,000 | Findings-up-front box; what we know; what remains unconfirmed; timeline; evidence notes; response/right of reply; CTA |
| Policy analysis | 1,600–2,200 | What changed; background; who benefits/loses; legal or regulatory stakes; critique; alternatives; CTA |
| How-to guide | 1,400–2,000 | Purpose; legal boundary; steps; checklist; common mistakes; example template; CTA |
| Case study | 1,800–2,400 | Context; actors; timeline; evidence; lessons; further reading |
| Toolkit | 800–1,400 | Checklist; downloadable template; FAQ; escalation paths; safety note |
| Multimedia outline | 600–1,000 | Hook; segment-by-segment breakdown; visuals/audio; quote candidates; supporting sources; CTA |
| Brief update | 500–900 | What happened; why it matters; what to watch; related evergreen links |

Governance is where 2IA can become unusually strong. The live site already hints at a source review standard and a report disposition ledger. That should be formalized into public publication rules: separate confirmed facts from inference; keep source notes; minimize harm; preserve correction pathways; publish a right-of-reply policy; and disclose how AI, if used, is limited. Those ideas align well with SPJ’s ethics code, the IFCN commitment to transparent fact-checking, NIST’s AI risk-management guidance, and the Santa Clara Principles’ emphasis on transparency, due process, fairness, and appeal in moderation systems. citeturn3view0turn20view0turn20view1turn20view2turn20view3turn20view4

I would formalize the editorial workflow like this:

| Editorial stage | Mandatory rule |
|---|---|
| Intake | Classify submissions: publishable, background-only, duplicate, defer, reject |
| Drafting | Every strong factual claim gets a source note or evidence reference |
| Fact-check | Mark each substantive assertion as confirmed, corroborated, disputed, inferred, or unknown |
| Sensitivity review | Remove unnecessary personal data; review harm to bystanders, victims, minors |
| AI review | If AI was used, document where and ensure human signoff |
| Right of reply | Offer reply to named organizations or persons in investigative pieces |
| Publish | Include author, date, update date, and related reading |
| Corrections | Maintain visible correction log and update history |
| Moderation | Publish a rules page with notice and appeal logic, not opaque whim |

For CMS, my ranking is straightforward.

| CMS option | Recommendation | Why |
|---|---|---|
| WordPress | **Best fit** | The live site is already WordPress-like; WordPress supports revisions, roles/capabilities, and differentiated post templates. That makes it ideal for issue hubs, investigations, guides, campaign pages, and governance docs without a rebuild. citeturn3view0turn19view6turn19view7turn19view8 |
| Ghost | Strong secondary option | Best if 2IA becomes newsletter-first or membership-first. Ghost has built-in newsletter flows and native analytics controls, but a research-heavy archive with multiple content types usually fits WordPress better. citeturn19view9 |
| Headless stack | Only if engineering-first | This adds flexibility but also complexity. It is overkill unless 2IA plans custom applications, datasets, or advanced interactive tools soon. |

If 2IA stays on WordPress, I would create custom editorial types for **Issue Hub**, **Investigation**, **Policy Analysis**, **Guide**, **Toolkit**, **Case Study**, **Campaign**, and **Update**. That is where WordPress stops being “a blog” and becomes a publication system. citeturn19view8turn19view7

## Roadmap, competitor comparison, and risk matrix

The implementation roadmap below assumes no major design rebuild and a lean team: one editorial lead, two writer-researchers, one part-time developer, one part-time designer, and shared fact-check/legal review. These are planning assumptions, not sourced industry benchmarks.

| Phase | Timing | Deliverables | Estimated output |
|---|---|---|---:|
| Foundation | Weeks 1–2 | Brand cleanup, IA, content model, style guide, methodology, corrections policy, metadata conventions | — |
| Core trust pages | Weeks 3–4 | Home, Start Here, About, Methodology, Support, Newsletter, Donate, Volunteer | 8,000–10,000 words |
| Issue hubs | Weeks 5–8 | Six priority issue hubs | 12,000–14,000 words |
| Guides and toolkits | Weeks 9–12 | FOIA guide, lawful contact guide, OSINT checklist, redaction guide, source review guide, correction toolkit | 9,000–11,000 words |
| Reporting layer | Weeks 13–16 | Two investigations, two policy analyses, two case studies | 13,000–15,000 words |
| Optimization | Weeks 17–20 | Internal linking pass, schema, sitemap verification, search console setup, onboarding emails, donation funnel test | — |
| Ongoing cadence | Monthly | 2 large pieces + 2 mid-sized guides/updates + 1 campaign or toolkit refresh | 5,000–7,000 words/month |

The competitors below show what 2IA should learn from, using only official site signals and official site content rather than third-party traffic estimates.