Emergency static conversion and production publish for a large-scale website

Emergency static HTML publish of the minimum required pages and features on a large commercial site, after mapping mixed-stack dynamic dependencies.

Key points

  • Emergency static conversion of a large commercial website with usage on the order of millions of people in the past 90 days
  • Changes to the top page and 262 HTML files
  • Investigation of dependencies across multiple existing technologies
Area of work
Development / implementation
Period
October 2026

Background

On a large-scale website with active users on the order of millions, I carried out emergency work to publish the minimum required pages and features as static HTML, because of system constraints.
I investigated the existing environment — CakePHP, Movable Type, SSI, JavaScript, and other mixed technologies — and mapped dependencies on dynamic processing. I changed the setup so it would run in a static environment while keeping the existing design and the paths that were still needed.
I mainly handled the technical investigation, implementation approach, changes, verification, and production publish. Using Claude Code, production publish was completed in 28 total hours including meetings.

Challenge

  • Existing pages that depended on dynamic processing such as PHP, SSI, and APIs had to be displayable in a static environment
  • Multiple technologies and generations of implementation were mixed, so the impact of a change was hard to see
  • Server constraints meant some existing JavaScript and external libraries did not run correctly
  • Required paths had to be kept, while paths to features and pages that would not work after static conversion had to be sorted out
  • As emergency work, investigation, implementation, verification, and publish had to move in a short time

What I did

  • Investigated CakePHP, Movable Type, SSI, and JavaScript dependencies and listed the changes needed for static conversion
  • Converted the top page and 262 lower-level pages to static HTML, based on the existing HTML
  • Replaced PHP dynamic output with static HTML or references to already generated files
  • Adjusted sales paths, page-to-page links, and asset paths
  • Visually checked display issues caused by SSI being disabled, and sorted paths to the affected pages
  • Placed required JavaScript libraries locally where external CDN loads failed
  • Set up a local review environment, verified on staging, and handled the production publish
  • Used Claude Code for investigation and changes across many files, and documented what changed and what to watch

What changed

  • Completed static conversion of the top page and the in-scope pages
  • Kept the required display and sales paths in the static environment
  • Resolved JavaScript display issues found on staging
  • Separated out-of-scope pages and features, and limited what was published
  • Completed production publish on a newly provisioned server and obtained client confirmation

Design notes

Map existing-system dependencies and limit the static-conversion scope

Rather than stripping all PHP, SSI, and API processing, I separated what the page still needed in order to display from what would not work after static conversion. I also distinguished SSI present in the code from SSI that actually caused display issues, and chose what to fix from visual checks. I did not rebuild the existing setup; I limited changes to what the publish requirements needed, which kept the change set and the verification set smaller.

Split cross-file implementation by AI from human display and quality judgment

I used Claude Code to investigate dependencies across files and to edit HTML and JavaScript. Display in the browser, user paths, and what to publish were judged not only from code analysis but from visual checks and matching against the requirements. AI handled investigation and implementation, while a human owned scope and verification, which made a short-timescale change possible in a complex existing environment.

What improved

On a large-scale website that mixed several technologies, I was almost solely responsible from investigating the existing system through static conversion, verification, and production publish. Combining cross-file implementation by an AI coding agent with technical judgment and visual checks, the emergency publish was completed in 28 total hours including meetings.

Notes

  • Completed from technical investigation through production publish in 28 total hours including meetings
  • Converted multiple pages to static HTML, including 262 HTML files
  • Mapped dependencies on existing dynamic processing and built a minimum publishable state
  • Gained practical experience of cross-cutting changes with an AI coding agent
  • Documented what changed and the remaining constraints for later maintenance and follow-up