← Selected work

MMP platform work · Editorial publishing

Turn a client knowledge graph into a public answer site—without turning every visit into a PHP request.

I designed the system that generates hundreds of client-specific questions and answers, lets each client style a microsite, and publishes the finished site as static HTML behind its own custom hostname.

Role
Technical Director
Context
Multi-tenant business platform
Disclosure
Client-anonymous

The problem

The problem

The product team had been considering client landing pages for years, but a traditional request-routed application would make every public visit depend on PHP processes and database lookups. Once an internal AI search experience could explain a client’s knowledge graph, the opportunity became clearer: publish useful answers for the public as both knowledge sharing and an SEO surface.

What I built

The system, not just the screen.

A public layer for reviewed knowledge

Built a workflow that can generate a few hundred answer candidates from a client’s knowledge graph, then keep public publication behind human review. The same system holds the line between internal AI context and what a visitor can reasonably treat as a client’s public answer.

A branded microsite without a bespoke deployment

Built the configuration and provisioning path for client styling, a CNAME-based custom hostname, DNS verification, certificate activation, and the edge route needed to make the answer site feel like part of the client’s own web presence.

Build once expensively, surface forever cheaply

Created a static-site generator that renders the complete question-and-answer site into versioned HTML artifacts in R2. A Cloudflare Worker uses KV as a small routing layer to direct the hostname to the active artifact prefix, so public readers do not tie up application processes or database queries when the content has not changed.

System sketch

How the system works.

A simplified view of the system boundary and the work it moves through.

  1. Client knowledge graph
  2. Question generation + review
  3. Static-site renderer
  4. R2 artifact prefix
  5. Worker + KV route
  6. Custom answer site

Key decisions

Key decisions

  1. Treat public content as a generated artifact, not a database-rendered page on every request.
  2. Use R2 for static HTML, Worker KV for hostname-to-artifact routing, and custom CNAME records for client-owned delivery.
  3. Publish a complete new version before repointing the live site, preserving the existing public site if a build or third party fails.
  4. Make the hosting system generic enough to support a future landing-page builder, not only Answers.

What it enables

What it enables

The result is visually simple by intention and architecturally substantial: a client can surface reviewed knowledge on a branded public microsite, while the system pays the expensive rendering cost only when content changes and serves the finished answer pages cheaply at the edge.

Return to selected work

Similar problem?

Facing a similar kind of product or systems problem?

Tell me where the complexity is piling up. If there’s a strong fit, I’ll reply personally.

A few sentences is plenty.

Your note goes straight to me—no mailing list.