e80f4030cb
Align the campaign desk with quieter KPI strips, queues-first dashboard, shared shells, and advanced filters; capture Impeccable design context and the remaining simplify/critique debts on the roadmap.
3.3 KiB
Product
Register
product
Platform
web
Users
Two surfaces, one product.
/campanha (primary for design defaults): campaign coordination (geral, coordenador) and leaderships (lideranca) as first-class peers — staff need depth for territory, people, estimates, and agenda; leaderships need a simpler, phone-first path into their nucleus. Used in the field and on the go, often under time pressure through the 2026 calendar.
Public site: citizens and the base in Bahia first (news, petitions, donate, stay close to the mandate); institutional visitors second (press, partners, official voice).
Product Purpose
/campanha: field operations and electoral intelligence as one job — nuclei, people, estimates, agenda, and share kits, plus a live picture of territory and vote gap so the team can prioritize action. Nuclei, people, and estimates live here as the system of record, even when outreach uses pragmatic channels.
Public site: own the relationship with the base first (engagement channel the campaign controls); project the mandate’s official voice and credibility second.
Success near-term: /campanha is the daily ops tool with real nuclei, people, and estimates in use, and the public site is the owned citizen channel — both live, not one or the other.
Positioning
Sovereign political intelligence, organization, and community engagement — the destination. Pragmatic channels (e.g. WhatsApp) are acceptable shortcuts today; the product should not make those the permanent system of record.
Brand Personality
Socialist, clear, inspiring.
Voice and UI should feel like tools built by people who believe a better internet and stronger grassroots organization are possible — functional and respectful (Mastodon), builders of owned channels (Automattic), willing to reimagine workflows when the old ones fail (Hey.com), and rooted in social mobilization practice (Bonde.org) — without pretending the team never uses the platforms people already live on.
Anti-references
Not generic SaaS dashboards (purple gradients, hero-metric templates, identical card grids, AI-startup chrome). Not traditional Brazilian campaign kitsch (clipart flags, shouty all-caps, brochure clutter).
Design Principles
- Sovereignty as the horizon — own audience, data, and ops over time; Big Tech shortcuts (WhatsApp kits, share links) are fine for now when they help mobilization, but design should keep the campaign’s own records and workflows as the source of truth and leave room to reduce platform dependency later.
- Clarity under pressure — every screen earns its keep for field use; prefer plain language and obvious next actions over decoration.
- Depth and simplicity as peers — staff workflows can be rich; leadership paths stay light and phone-first without becoming a second-class product.
- Intelligence serves organization — electoral baseline and insights exist to decide where to act, not to impress.
- Inspire without kitsch — socialist and mobilizing in spirit; never shouty campaign brochure aesthetics.
Accessibility & Inclusion
WCAG 2.2 AA as the bar (contrast, keyboard, focus, reduced motion). Plus: larger touch targets for leadership / field phone use, and screen-reader priority on forms (labels, errors, and critical actions must be announced clearly).