Marketing Site Proposal · TKX Media

Tranzito × LADOT

A WordPress + Gutenberg marketing site for the Integrated Mobility Hubs program at tranzito.org/ladot.

ClientTranzito
PartnersLADOT · LA Metro
Timeline~8 weeks
Investment$8,000 – $10,000
01

Project Overview

Tranzito is partnering with LADOT and LA Metro to launch the Integrated Mobility Hubs (IMH) program — a network of physical transit hubs across Los Angeles that consolidate multimodal mobility, real-time transit information, and equitable access to subsidized transportation services.

This proposal covers the design and development of the public marketing site at tranzito.org/ladot, which will serve as the primary informational and acquisition layer for the IMH program. The site is scoped separately from the authenticated portal and CurbCMS admin surfaces, which are being handled by other vendors.

The marketing site has three audiences to serve:

02

Scope of Work

Work breaks down into four blocks — discovery, design, page inventory, and development — followed by an explanation of why we're building on Gutenberg rather than a third-party page builder.

2.1 Discovery & Information Architecture

A focused discovery phase to align on audience priorities, content strategy, and site structure before any design work begins.

  • Stakeholder kickoff and goals alignment session
  • Audience mapping (riders, partner cities, program stakeholders)
  • Sitemap and information architecture, built from scratch
  • Content inventory and gap analysis
  • Coordination touchpoint with Designworks to align on brand direction
2.2 Design

Visual design aligned to the Designworks-led brand direction (Unified Green palette, accessibility-compliant typography) and delivered as a polished, production-ready design system.

  • Style tile and design system foundation — colors, type scale, spacing, components — aligned to Designworks brand guidelines
  • Wireframes for all in-scope page templates
  • High-fidelity designs at mobile and desktop breakpoints
  • Component library suitable for Gutenberg block reuse
  • Two rounds of design revisions per template
2.3 Page Inventory

The site will include the following templates and pages. Final page count will be confirmed in discovery — this is the planning baseline.

Page / TemplatePurpose
HomeProgram overview, primary CTAs, audience segmentation entry points
How It WorksExplanation of mobility hubs, services, and how riders engage with the program
Find a HubInteractive map or directory of hub locations with filtering
For RidersConsumer-facing landing covering services, programs, and signup
Programs (UBM / LIFE)Subsidy program information, eligibility, and enrollment guidance
For Cities & PartnersB2B-facing page positioning the platform for other municipalities
AboutMission, team, LADOT/Metro partnership context
News / ResourcesIndex template plus single post / article template
Contact / SupportInquiry form, support routing, hours
FAQSearchable accordion of common questions
Legal & AccessibilityPrivacy, Terms, Accessibility statement (three short templates)
Total: approximately 10–12 unique page designs, plus three lightweight legal templates. Each design delivered for mobile and desktop breakpoints.
2.4 Development

The site will be developed in WordPress using the native Gutenberg block editor, giving Tranzito's team full control over content updates without requiring developer involvement post-launch.

  • WordPress installation, theme setup, and configuration
  • Custom Gutenberg block patterns matching the design system, so content editors can build new pages from approved components
  • Page templates and reusable block patterns for each section type (hero, feature grid, testimonial, CTA, content row, etc.)
  • Interactive hub locator (Find a Hub) with map and list views
  • Forms (Contact, Partner Inquiry) with email routing and spam protection
  • Responsive build across mobile, tablet, and desktop
  • SEO foundation: meta tags, structured data, XML sitemap, robots.txt
  • Performance optimization: image compression, lazy loading, caching
  • Accessibility implementation targeting WCAG 2.1 AA
  • Analytics integration (GA4 or equivalent, per Tranzito's preference)
  • Pre-launch QA across browsers and devices
  • Launch coordination and post-launch verification
2.5 Why Gutenberg

We're building this as a Gutenberg-native WordPress site rather than relying on a third-party page builder (Elementor, Divi, etc.). For a civic-facing site with a long operational horizon, this decision matters.

  • Editorial autonomy. Tranzito's content manager can update copy, swap images, add new pages, and assemble new layouts from approved block patterns — all without writing code or filing developer tickets.
  • Performance. Native blocks produce cleaner HTML and faster page loads than third-party builders, which matters for SEO and for users on slower mobile connections.
  • Maintainability. Gutenberg is the WordPress core editor and is supported indefinitely. Third-party builders introduce dependency risk and licensing overhead over a 5–10 year horizon.
  • Accessibility. Gutenberg's default markup is more accessible out of the box than most page builders, giving us a stronger WCAG 2.1 AA starting point.
03

Timeline

Targeting a roughly 8-week engagement from kickoff to launch, with the understanding that the Designworks brand direction needs to be substantially settled before our high-fidelity design work begins.

Phase 1 · Discovery Week 1

Kickoff & alignment

Audience alignment, sitemap, and content strategy. Stakeholder kickoff session sets goals and the rules of engagement.

Phase 2 · Design Weeks 2–4

Style tile through high-fidelity

Style tile, wireframes, and high-fidelity designs across all in-scope templates. Two revision rounds per template included.

Phase 3 · Development Weeks 4–7

Build, integrate, harden

Theme build, Gutenberg block patterns, page templates, hub locator, forms, SEO foundation, accessibility implementation. Development overlaps the tail end of design so velocity stays high.

Phase 4 · QA & Launch Week 8

Cross-browser QA & go-live

Cross-browser QA, accessibility audit, content load, launch, and post-launch verification. We do not consider the project complete until the site is live and stable in production.

Timeline assumption: Designworks brand direction is delivered no later than end of Week 1, and Tranzito feedback on each design and dev milestone is provided within 3 business days. Delays in either input will shift the launch date accordingly.
04

Investment

Total Fixed Fee
$8,000 – $10,000

Final fee within this range will be confirmed at the end of discovery, once the page count and feature scope are locked. Pricing covers all design, development, project management, QA, and launch activities outlined in Section 2.

Payment Schedule

MilestoneAmountTriggered By
Project kickoff50%Signed SOW, kickoff scheduled
Design approval25%Sign-off on high-fidelity designs
Launch25%Site live on production

What's Included

Ready to move? A signed SOW and the kickoff scheduled is all we need to start Week 1 of discovery. The earlier we lock the Designworks brand direction, the smoother Weeks 2–4 will run.