Google / CONTENT ENGINEERING
Writing the script for Google’s new publishing platform.
SYSTEMS TRANSLATION × HIGH-STAKES PUBLISHING
Translating design intent, component behavior, platform constraints, and stakeholder feedback into launch-ready content for Google’s enterprise CMS migration.
01 / SEE
I came on as a Content Author to migrate, build, test, document, and launch 134 pages in 22 days.
The work quickly became more technical. The new CMS needed a content system that could hold the design intent without asking every future publisher to become an engineer.
I moved upstream and my title changed with it: Content Engineer.
02 / SHAPE
Understand what the experience needed to do and what the platform could actually support.
Then turn that knowledge into content rules, authoring guidance, reusable patterns, and a publishing model Google teams could carry forward.
03 / TEST
The design, content architecture, and platform were all moving at once. I worked directly with design and engineering to preserve the intended experience.
I identified where components failed under real content, clarified constraints, documented component nuances, and wrote authoring guidelines that made it possible for Google teams to manage everything on their own after launch.
04 / SHIP
Five Google sites in less than six months.
01 — Public Policy
02 — Crisis Resilience
03 — Nonprofits
04 — Post-Quantum Computing
05 — Data Centers
05 / SCALE
Speed and quality stop competing when strategy, documentation, the system, and production model are designed together.
Next: Writing the script for Wayfair’s first Global Content Operations team.