Content Management for All Media
Orchestrating the Modern Media Mix
Two decades of CMS work creates perspective that's hard to fake. We've built on WordPress and Drupal through their entire arc: from classic server-rendered installs and custom theme development to headless API-first configurations that feed modern frontends. We understand why those platforms won, where they fall short today, and how to extend or replace them without disrupting editorial teams who depend on them.
Our current work centers on headless CMS architecture and custom content backends built with Node.js and TypeScript. Whether that means configuring Sanity, Payload, or Contentful, or engineering a purpose-built content API from scratch, the goal is the same: a clean separation between content management and presentation, paired with rich media pipelines that handle image optimization, video transcoding, and automated asset metadata at scale.
Not every client needs a full CMS replacement. Often the highest-value work is adding modern capabilities to what already exists: AI-generated alt text and structured metadata, social media syndication, Cloudinary DAM integration, or multilingual content architecture. We can augment a legacy WordPress or Drupal install with these features without touching its core, giving teams real improvements without the disruption of migration. Several of these capabilities are available as open-source tools clients can take direct ownership of.
- AI content enrichment as a repeatable service: WCAG-compliant alt text generation via Cloudinary and Mistral vision API, automated JSON-LD schema generation from page content, and structured metadata enrichment delivered as standalone tools that integrate into existing workflows
- Configuring CMS platforms for editorial independence: custom post types, content schemas, and publishing workflows that non-technical teams can operate without developer involvement
- Headless CMS architecture and custom content API backends in TypeScript and Node.js
- WordPress and Drupal: deep theming, custom post types, plugin and module development, and headless configurations
- Rich media management via Cloudinary DAM, including AI-generated WCAG-compliant alt text and automated image optimization pipelines
What This Looks Like in Practice
Legacy CMS Augmentation
Picture an existing WordPress site gaining AI-powered alt text generation, automated JSON-LD schema, and a Cloudinary media pipeline without a platform migration. Editorial teams keep their familiar workflow while the site gains modern performance, accessibility compliance, and structured data that meaningfully improves search visibility.
Headless Editorial Platform
Consider a high-traffic news platform built on a headless CMS feeding a Next.js frontend, with a custom content API handling multilingual editorial workflows, subscription-gated content, and a media pipeline that processes and delivers assets across web and mobile from a single source of truth.
Omnichannel Content Orchestration
Envision a single content entry that automatically formats and distributes to a website, a mobile app, and social channels simultaneously, with images optimized per platform and metadata enriched at publish time rather than manually on each surface.
Tech Stack
- CMS Platforms
- WordPressDrupalSanityStrapi
- Languages
- TypeScriptJavaScriptPHPPython
- Media Pipeline
- CloudinaryFFmpegSharpImageMagick
- Backend
- Node.jsExpressHono
- Data
- PostgreSQLMySQLSQLite
- Infrastructure
- DockernginxCI/CD