Enterprise Drupal
website development
in Redwood City

Redwood City is the seat of San Mateo County, and the publishing pattern that follows is unmistakable: agendas and minutes, permit and planning notices, court calendars, board packets, and public-notice material that must remain retrievable long after anyone stops linking to it. That is a records problem before it is a design problem. Drupal answers it in core with structured entities, full revision history, granular role permissions and translation, so one office can publish independently without an administrator opening the gate each time. Proprietary systems tend to meter those capabilities, and a WordPress build reaches the same place only through a plugin stack that someone has to keep alive. For a body with statutory obligations, capability in core beats capability by assembly.

A full Drupal engagement covers information architecture and content modelling, theme development, custom modules, version upgrades, integrations, multi-site configurations and ongoing managed maintenance. Public-sector and health-adjacent bodies around Redwood City typically need three additions specified up front: accessibility conformance evidenced rather than asserted, records retention that distinguishes an amendable page from a fixed public notice, and a delegation model letting a planning office publish without touching what the clerk's office owns. Those requirements are settled during architecture, because retrofitting a permission model onto a live site is the painful way to learn them.

Drupal 7 is past end of life, which turns a deferred upgrade into an exposure. The migration starts with an audit separating content still in active use from the accumulated remainder, and with a URL map, because for a county-seat site the old paths are cited in agendas, staff reports and third-party documents nobody will reissue. Target architecture is usually simpler than the legacy site — long-lived public sites collect content types that outlived their purpose. Content moves in stages against a parallel environment, redirects are written before cutover rather than reconstructed afterwards, and a build of this complexity commonly occupies 12–20 weeks.

Custom modules are where a public-sector Drupal site stops fighting its own workflow. The recurring builds around Redwood City: agenda and minutes packages that assemble a meeting record from individual items and publish it on a statutory schedule, permit and application status lookups that read from a back-office system without exposing it, public-notice types carrying a publication window that archive themselves when it closes, and redaction-aware document handling for material that is public only in part. Each is written to Drupal coding standards with tests, so a security release never forces a choice between patching and keeping the workflow.

A Drupal site is fast when its caching layers are chosen deliberately. Page cache and dynamic page cache handle anonymous traffic, a reverse proxy or CDN absorbs the rest, render caching with correct cache tags keeps invalidation precise instead of global, and slow database queries are found by profiling rather than by guesswork. Redwood City sites see a specific load shape: quiet for days, then a council decision, a planning notice or a downtown event listing produces a sharp burst on a handful of URLs. The design question is which pages need to be personalised at all — pages served identically to everyone belong at the edge, and the burst never reaches the application.

Drupal security advisories arrive on a published schedule, and the discipline is in the response window. Managed maintenance covers advisory triage on the day of release, tracking contributed modules for abandonment, applying core updates on a regular cadence, and restoring backups on a test schedule so recovery is rehearsed. Public bodies in San Mateo County add requirements of their own: administrative access behind single sign-on, an audit trail that answers who changed a published notice, hardening reviews wherever forms collect resident information, and a documented disclosure route. Unmaintained Drupal is not stable — it is simply not yet patched.

Drupal serves and consumes structured data through JSON:API and service modules, which suits a county-seat site that is rarely the system of record for its own content. The connections recurring locally are civic: geographic information systems behind parcel, zoning and district lookups, permit and licensing back-office systems, meeting and legislative management platforms, open-data catalogues expecting a stable machine-readable feed, and identity federation for staff accounts. The rule keeping such an estate maintainable is to name one master per field and keep synchronisation one-way wherever the workflow allows, so a display copy can never quietly disagree with the official record.

Expect 12–24 weeks end to end. The long pole is rarely the front end; it is agreeing an information architecture that many departments can share, plus the review chain each publication has to clear. Redwood City is the seat of San Mateo County, so the local pattern is public sector: agendas, minutes, permits and notices that stay retrievable for years, served under state and federal accessibility rules, on a site where several offices publish independently. Drupal handles that through granular roles, revision history and structured records, but each of those is a design decision with a schedule attached, and the figure is fixed after those decisions are made.