CivicDeck

Issues

How Issues Work

The Issues tab is where CivicDeck organizes the topics that keep showing up in headlines, meetings, and elections—without turning it into a feed.

An Issue is the "umbrella" topic (example: housing, water, energy, public lands, zoning, data centers, healthcare). Most news isn't a brand-new issue—it's an update to an issue that's already in motion. CivicDeck is meant to keep that subject organized so you can follow up on your own time.

Issues also need to be viewed at the right level. CivicDeck is designed to let you see issues across layers:

  • World
  • United States
  • State
  • Local

And then tie each issue to the structure around it:

  • Initiatives = specific proposals or ballot/community-input items connected to an issue
  • Offices / Officials = who has authority and accountability on the issue
  • Documents = the receipts (official sources, filings, agendas, minutes, etc.)

Collecting Cards

In CivicDeck, cards are where the receipts live—and Issues are some of the most important cards you can collect.

When you watch an issue, you're collecting a card that becomes your "home base" for that subject:

  • what the issue is (plain language)
  • what changed recently (updates tied to sources)
  • who is involved (offices/officials connected to the issue)
  • what actions are attached (initiatives, votes, meetings, community input)
  • where the receipts are (documents and credible media attached to the card)

This is the "follow up later" feature: a soundbite becomes a saved subject—with receipts attached—so you can stay with the issue instead of chasing noise.

Advancing by building your Issue deck

One simple way to grow in CivicDeck is by building a stronger deck around real subjects.

When you collect an Issue card, you can also collect the connected cards that explain it:

  • the related Initiatives
  • the key Documents
  • the responsible Offices / Officials

The more complete your deck is on an issue—the subject, the actions, and the receipts—the easier it becomes to understand what's happening and participate responsibly (on your own time, without needing to argue online).

(Down the road, CivicDeck can support engagement-based progression too. For now, Issues starts with the simplest form of progress: collect the right cards, with the receipts attached.)

Volunteers (how to help / roles)

Our issue list may be long, but it's meant to be defined and stable. Issues aren't created by headlines or media cycles—they're based on the responsibilities of government. Once the baseline list is in place, creating brand-new issue cards should be uncommon.

That's why CivicDeck keeps issue cards simple and consistent. We'll use the same basic structure for every issue—so adding or updating an issue later is mostly filling in fields, not reinventing the wheel.

Volunteer help here is light but important:

  • keeping issue names consistent (so "Housing" doesn't become five different versions)
  • improving plain-language descriptions so they stay neutral and easy to scan
  • testing the structure with a handful of example issues (just enough to validate it)

If you want to help, email: volunteer@civicdeck.app

Media (reputable compilations tied to cards — no feed)

CivicDeck won't run on a video feed.

In CivicDeck, media is attached to Issue cards—so coverage stays tied to the exact subject it relates to. The goal isn't "more content." The goal is better receipts:

  • documents first (official sources)
  • plus a small amount of credible media when it helps clarify what was said or decided

Volunteer help can be important here too—especially media curators who can attach a handful of credible clips to prototype this function.

Progress (where we are right now)

CivicDeck is built in visible phases so supporters and volunteers can see what's real, what's in progress, and what's next.

What we track right now:

  • Design (Figma prototype): 5%
  • Build (Back office foundation): 10%
  • Scale (Volunteer onboarding): 1%
  • Donations / Sponsors: 0.5%

As those numbers move, you'll know exactly where effort is going and what help is needed.

This website is a "demo shell"—an explainer. Follow along for updates as the Figma prototype evolves and as progress continues in the back office.