FivePaths

SFMTA.com

SFMTA Homepage on Desktop
www.sfmta.com
Client
SFMTA
Sector

SFMTA.com helps people navigate San Francisco's transportation system, from finding a route or checking an arrival to understanding a fare or following a street improvement project. Behind those public pages, agency staff manage a large body of information with established publishing and review practices.

FivePaths rebuilt the site from Drupal 7 to Drupal 10 with a deliberate goal: make the transition as invisible as possible. We worked to preserve the existing visual design and the behavior that riders and staff depended on, while replacing the underlying implementation with a foundation that would be easier to maintain and extend.

That required understanding years of accumulated features, migrating content and its relationships, and preparing a heavily used public website for real traffic. SFMTA's team helped identify requirements, explain existing workflows and test the rebuilt site. FivePaths handled the migration and development.

Finding a route is one of the everyday tasks the rebuild needed to preserve. Current site, captured November 13, 2026.

Understand the site people already relied on

The old website had evolved over many years. Much of its custom behavior lived in procedural code written for Drupal 7, with decisions and exceptions added as the agency's needs changed. Rebuilding it meant finding out which features were still used and understanding the work each one performed.

We carried out a detailed feature analysis covering custom code, fields, content displays and blocks. The inventory connected existing behavior with its replacement in modern Drupal. Map displays, image galleries and project timelines, for example, needed to retain their purpose even as their implementation moved into dedicated classes and formatters.

Project pages combine several kinds of content and relationships. The feature analysis helped identify the behavior that needed to carry forward. Current site, captured November 13, 2026.

This analysis also distinguished an obsolete technical component from a feature that still mattered. An old display configuration could be retired because a new formatter took over its job. Keeping that distinction clear helped us make deliberate decisions about what to carry forward.

SFMTA supplied the context that code alone could not explain. Its staff knew how information was maintained, which exceptions were intentional and what editors expected to happen when they changed a page. Their testing gave us a way to check the rebuilt behavior against those expectations throughout development.

Preserve the details that make the site useful

Transit stop information showed why this work needed both technical analysis and client knowledge. The website and the General Transit Feed Specification, or GTFS, feed could legitimately contain different information. The feed described current service, while the website could retain stops that remained part of the network even when they were absent from the current feed.

Those differences mattered to someone standing at a marked stop and trying to understand where to go. They also mattered to staff maintaining route and stop information. A difference between the two systems needed to be visible so the team could decide what to keep or correct.

We built a stop audit tool that compared the website's stops with the GTFS feed. It reported differences by route and direction, including stops present only in the feed or only on the website. This gave SFMTA a practical way to review discrepancies while retaining information it intentionally wanted on the site.

Client testing also caught details that made the public pages useful. A nearby-stop list needed the route indicators showing which services called there. Shelter-maintenance requests needed their separate links. These were small parts of the interface with specific jobs to do, and the team checked them against the old site.

Nearby stops include route indicators so riders can see which services they offer. This current stop page also brings together arrivals, maps and trip planning. Captured November 13, 2026.

Editorial work needed the same care. We developed special preview styling so editors could review a draft in the presentation visitors would see, with a visible notice identifying it as a draft. That let staff assess a page's appearance while keeping its publication state clear.

The migration supported this continuity at the content level. We preserved content identifiers and page aliases, handled translated field values, and addressed collisions between existing paths and imported redirects. We also carried image descriptions from legacy content into the new media structure, including metadata attached to images embedded in formatted text.

Fares provided an early test case because they brought together content fields, translations, revisions and publishing review. We asked SFMTA to check whether content had migrated correctly and whether staff could edit it, create drafts, submit changes for review, approve them and manage translations. Using one content type to exercise those connected tasks gave the review a concrete starting point for behavior shared across the site.

Prepare for real traffic

Performance was a central launch concern. A busy public transportation website needs to respond reliably when people depend on it, and realistic traffic is difficult to reproduce fully before launch.

Pantheon provided the hosting and caching foundation. Our preparation focused on the application code running within it. We used New Relic to investigate complex queries and long-running processes, then optimized them ahead of launch to reduce the risk of slowdowns under traffic.

Readiness also depended on use by the people who knew the site. The client and staff spent time exercising the rebuilt workflows, reporting problems and checking the changes. Confidence grew as they continued using it without finding further issues in the tasks they tried.

The intended launch experience was uneventful. We preserved as much of the public design as possible and worked toward a transition in which people could continue finding information and staff could continue publishing it. The 2024 relaunch was followed by continued monitoring and adjustments to caching as the site settled into production use.

Make the next change easier

The rebuild changed how we could understand and maintain the custom code. Modern Drupal, built on Symfony, gives us explicit services and extension points for organizing behavior. We can more readily see which code runs when and keep the logic for a particular feature together in a module or class.

For SFMTA, that meant translating accumulated Drupal 7 behavior into components with clearer responsibilities. The map block brought map-selection behavior into a dedicated class. Other components handled galleries, timelines and contextual information. Registered services and event subscribers gave functions such as breadcrumbs and language handling defined places in the application.

That organization makes later changes easier to follow. When a feature needs adjustment, its related logic has an identifiable home, and we can assess how the change interacts with the rest of the site. The move also renewed the underlying platform for ongoing PHP compatibility and security maintenance.

Keep supporting the site after launch

Our work continued beyond the rebuild. We have supported the site through maintenance, integration changes and further improvements, working with SFMTA's team as its needs evolve. Later work has included Muni Alerts updates and further investigation of caching behavior.

Muni Alerts is part of the continuing work on rider information after the rebuild. Current site, captured November 13, 2026.

In 2026, we added automated tests around the editorial workflows we continue to support. They exercise draft creation, review and publication, including keeping the published version available while a new draft is being revised. Other tests cover permissions and media handling, including required alternative text and the rendering of published images.

The suite has helped uncover defects during ongoing development and gives us repeatable checks as the implementation changes. It complements the client testing that helped shape the rebuild and supports the continuing work of maintaining familiar behavior on an evolving platform.

Built Using

Drupal

Venerable open-source CMS for managing large sites efficiently

Salesforce

Industry-standard CRM with powerful extensibility features

Pantheon

Seasoned host with a variety of developer-friendly features

OpenStreetMap

Crowd-sourced geo-database used as data source for countless maps

ArcGIS

Industry-standard GIS software

GTFS

De-facto standard for transit agencies to publish their services

YouTube

World's largest video hosting provider that can be embedded and integrated

MapLibre

Highly performant open source map rendering library

Docker

Container management for developing reproducible tech stacks

PHPStorm

Indispensable development environment for all our web projects