Drupal, from a system that outgrew its last build to one a team can maintain.
Four related capabilities for federal, state, and city government and commercial teams — delivered by a single senior architect and scoped to what you actually need to run and keep running.
Off Drupal 7, onto Drupal 10 or 11
Drupal 7 reached end-of-life in January 2025. A migration is a content and structure move, not a rebuild: the goal is to carry forward what the platform already does while shedding what it no longer needs. The work is planned so it can be paused, checked, and rolled back.
- Content-type and field audits, with a documented mapping from the source site
- Migrate API pipelines for nodes, taxonomy, users, files, and media
- URL redirect strategy to preserve search rankings and inbound links
- Theme rebuild on a maintained base, or component migration where a design is kept
- A staged cutover plan with a defined rollback path
Content models and platforms built to be maintained
Twelve years across Drupal 6 through 11, including an 18-site multisite platform. Architecture decisions are made for the team that will inherit them: fewer content types, configuration in code, and dependencies chosen for their maintenance record.
- Content modeling: content types, fields, taxonomy, and view modes
- Multisite and multi-domain platforms with shared code and separate content
- Configuration management and environment-specific config splits
- Views, Layout Builder, and structured content for reuse
- Editorial workflows, revisions, and role-based permissions
WCAG 2.1 AA, handled in the build
Accessibility is treated as an engineering requirement, not a final audit. Problems are fixed at the source — in the theme, the components, and the content model — so they do not return with the next content edit.
- Remediation of existing sites to WCAG 2.1 Level AA
- Keyboard operability, focus order, and visible focus states
- Semantic markup, headings, landmarks, and ARIA only where needed
- Color-contrast review against the 4.5:1 and 3:1 thresholds
- Accessible components and editor guidance so content stays conformant
Delivery pipelines and the systems Drupal has to talk to
Docker-based local environments and CI/CD so deploys are repeatable and reviewable. Single sign-on and third-party integrations built and documented, including Okta SSO with Drupal.
- Dockerized local development matched to the hosting environment
- CI/CD pipelines with automated build, test, and deploy steps
- Okta single sign-on integrated with Drupal authentication
- Search (Apache Solr), caching (Varnish), and CDN (Akamai) configuration
- Integrations with external systems such as Salesforce
Platforms & tools
Technologies the principal has worked with in production. Depth varies by tool; ask for specifics on any line.
| Area | Tools & platforms |
|---|---|
| CMS | Drupal 6, 7, 8, 9, 10, 11 |
| Hosting | Acquia Cloud, AWS |
| Performance | Varnish, Akamai CDN |
| Search | Apache Solr |
| Auth | Okta single sign-on |
| DevSecOps | Docker, CI/CD pipelines |
| Integrations | Salesforce |
| Migration | Drupal Migrate API, WordPress-to-Drupal consolidation |
Have a Drupal problem that fits one of these?
Start with a short scope call. If it is not a fit, you will get a straight answer and, where possible, a referral.