Campaign website
A responsive public presence with issue information, media, resources, volunteer opportunities, and prominent routes into the main actions.
Campaign platform / CRM / acquisition
End Property Tax Now
03 / 11A public campaign website connected to supporter intake, event discovery, book offers, publishing, and a custom administrative system.
Public homepage: campaign identity, primary actions, and supporter intake.
THE BRIEF
What the project
needed to do.
The project needed to serve several different intentions without turning into a collection of disconnected landing pages. A visitor might want to understand the issue, express support, attend an event, request a speaker, volunteer, or get the book. Each path needed a clear next step and a way for the team to follow up.
MY APPROACH
Connecting the design
with the work.
I brought the public experience and the operational systems into the same project: a recognizable campaign identity, purpose-built pages, structured forms, and a backend that preserves the source and intent of an inquiry. The website is the visible layer. The work also includes the records, publishing tools, and integration handling behind those actions.
PROJECT SCOPE
The work in detail.
Supporter capture
Structured intake with email validation, duplicate handling, consent choices, and a distinction between an online expression of support and an official ballot petition.
Truth Tour events
Event listings with dates, locations, flyer artwork, ticket links where available, and map directions. Private-event addresses are handled separately.
Book & resource offers
Dedicated presentation for books, bulk orders, group use, and related campaign resources instead of sending every visitor through the same generic form.
CRM & publishing
A shared administrative foundation for submissions, status changes, notes, filters, exports, and editable website content.
Connected follow-up
Form-specific connections to email, CRM, live-event, and messaging workflows, with integration results recorded for operational review.
THE EXPERIENCE
How the pieces connect.
- 01
Discover
Understand the campaign and choose a relevant action.
- 02
Act
Submit a supporter form, find an event, or explore the book.
- 03
Record
Preserve the submission and its source in the backend.
- 04
Follow up
Route the record into the appropriate team and communication workflow.
01 / PROJECT DETAIL
Different actions need different workflows.
Supporter signups, newsletter subscriptions, meeting requests, volunteer inquiries, and event registrations do not all mean the same thing. The implementation keeps those entry points distinguishable, so an administrator can understand why a person reached out and what should happen next.
The event layer also carries practical detail: flyer assets, start times, venue information, directions, and public or private status. That makes the tour useful as an actual planning tool, not just a promotional image on a page.
02 / PROJECT DETAIL
The system behind the public pages.
The source includes Firebase-backed records, server-side form handling, administrative lead tools, editable publishing, and connections to services such as GHL, AWeber, and event messaging. Integration behavior is specific to the form and workflow rather than one blanket rule for the entire brand.
Validation, rate limiting, duplicate handling, source labels, and delivery-status fields are part of the implementation. These details matter when a website has to support ongoing work after a visitor presses submit.
SELECTED SCREENS
A closer look at the work.
HAVE SOMETHING IN MIND?