Anticode Open builder

Building a political campaign website voters and volunteers can use

A political campaign website has three audiences: voters deciding who you are, supporters ready to help, and journalists checking facts. It needs a clear biography, plain policy pages, a volunteer sign-up and an events list, plus whatever notices election law requires where you're standing. Anticode builds those parts; the campaign is responsible for every legal and financial rule.

Updated · By the Anticode team

Rules come first, and they're yours

Election law differs between countries and often between levels of office. It can govern what a campaign must print on its materials (an imprint or "paid for by" line), who may donate, how much, what details must be collected from donors, how spending is reported, and how personal data about voters is used. Check the rules with your election authority or agent before the site goes live. Nothing on this page, or anything Anticode writes, is legal advice, and a website builder can't confirm your compliance.

The pages a campaign needs

  1. Home: the candidate's name, the office and area, the election date, one line on why they're standing, and two buttons: volunteer and sign up for updates.
  2. About the candidate: where they live, their work and community involvement, and why they're running, written in their own voice.
  3. Policies: one page per priority, with what they'd do and how.
  4. Get involved: volunteering roles, and how to request a poster or a yard sign.
  5. Events: canvassing sessions, public meetings and hustings.
  6. News or press: statements and announcements, with a media contact.
  7. Contact: a form and the campaign's office details.

Policy pages that people read

Voters skim, and opponents quote. Each policy page works best with a plain heading, a two-sentence summary, the specific commitments as a short list, and a paragraph on how it would be done. Keep the language concrete and local where the office is local: name the roads, the schools, the services. Keep policies in a CMS collection so each has its own address that can be shared, and so the team can correct a detail quickly without rebuilding the site.

Volunteer and supporter sign-ups

Most campaign work runs on volunteers, so the sign-up should capture what you need to deploy them. A custom form tied to a site function can carry up to 30 plain-text fields: name, email, phone, postcode or ward, availability (weekday evenings, weekends), and what they'd like to do (door-knocking, phone calls, leaflet delivery, data entry, hosting a poster). For supporters who only want updates, the newsletter form asks for an email alone and can send it to Mailchimp or Kit.

Connectors can pass volunteer sign-ups to a Google Sheet, Airtable or a Slack channel for organisers. Each submission is sent once, without retries, so check the dashboard copy if a connector fails. See volunteer sign-up process for the flow after someone signs up.

Donations, only where permitted

Anticode sites don't process payments themselves. If the campaign is allowed to accept online donations and has a compliant processor, buy buttons can point to a payment link from Stripe Payment Links, PayPal or a similar provider. Many jurisdictions require donor details, eligibility declarations and limits that a simple payment link may not capture, so a dedicated political donations platform is often the right tool; link to it instead. The campaign decides which applies.

Events in the CMS

Keep events in a CMS collection with date, time, place, type and a short description, and update it as plans change. Remove past events or move them to an archive so supporters don't turn up to last week's canvass. Maps can't be embedded on published pages; give the address and a map link. For an RSVP, a short custom form works; see collect event RSVPs.

Data protection and security

Volunteer and supporter details are personal data, and political opinions are treated as especially sensitive under some data protection laws. Collect only what you need and say how you'll use it. Anticode writes a starting Privacy Policy from what the site actually collects; the campaign must check and adapt it. Submissions are sealed at rest, an access log records the last 200 reads, exports and deletes, and the site can't be published until the account owner and the person publishing use two-factor sign-in. That matters when volunteers come and go.

Design for trust and speed

Swiss (Inter Tight) or Editorial (Geist) with a single action colour in your campaign's shade keeps the site clean and fast on a phone at the door. Design-engine pages carry no scripts and no third-party trackers. Use real photos of the candidate in the community, and write alt text for each.

What Anticode doesn't do for campaigns

  • No compliance checks for election law, imprints or donation rules.
  • No donation processing, donor records or spending reports.
  • No voter database, canvassing app or phone-banking tools.
  • English-language sites only, which matters in multilingual constituencies.

Questions people ask

Can a political campaign website take donations through Anticode?

Only through links to a payment provider or donations platform, and only where the campaign has confirmed it's permitted and compliant.

What should a candidate website include first?

The candidate's name, office, area and election date, a short reason for standing, and buttons to volunteer and sign up for updates.

Where do volunteer sign-ups go?

They're saved and sealed in your dashboard, can be emailed to you, and can be sent to Google Sheets, Airtable or Slack.