01 · The problem
A flagship publishing site has to move stories, photography, and video at global scale without fragmenting the reader experience or slowing editorial teams.
National Geographic is one of the world's most recognized science, exploration, and storytelling brands. The digital platform at nationalgeographic.com delivers journalism, photography, and video to a global audience.
02 · My role
Technical Lead · enterprise web delivery (Myridius)
03 · The result
Contributed to enterprise web delivery on a high-visibility National Geographic program through Myridius. Collaborated with design, QA, and delivery on the public National Geographic experience, with attention to reusable front-end patterns and production-quality publishing workflows.
04 · Architecture
- 01
Public web experience at nationalgeographic.com
- 02
Story, photography, and video surfaces for a global audience
- 03
Reusable front-end patterns shared across publishing pages
- 04
Structured delivery with design, QA, and multi-team coordination
The story
- The constraints
- A flagship publishing brand. Story hierarchy and photography come first. This diagram is generalized — not an internal National Geographic topology.
- The hard part
- Reusable front-end patterns on a site that must still feel like a magazine, not a component catalog.
- The trade-off
- Shared UI keeps teams aligned. Over-abstracting a story page makes editors fight the template.
- What broke
- Nothing I can publish as a client incident. The hard part was editorial consistency, not a named outage.
- What changed
- The public nationalgeographic.com experience is the record.
- What I would do differently
- I would keep contracts and names boring, and I would not invent a parallel design system beside the one authors already use.
Diagram
Editorial
- Purpose
- Stories, photography, video.
- Trade-off
- Hierarchy over chrome.
- Scale
- Global readership.
Implementation
- Homepage and story surfaces for a global readership
- Photography-forward layouts that keep editorial hierarchy clear
- Reusable UI patterns for publishing teams
- Cross-functional delivery with design and QA
Challenges & outcomes
Challenges
- Shipping on a high-visibility brand without breaking reader trust
- Keeping component patterns consistent across a large publishing surface
- Working inside structured client frameworks without blocking progress
Outcomes
- Supported a flagship National Geographic publishing experience used worldwide
- Improved maintainability of shared front-end patterns on a large content site
Lessons
- Editorial platforms succeed when engineering respects story hierarchy
- Reusable UI only sticks when teams agree on naming and contracts
- High-visibility clients reward clarity in documentation and demos
Related writing
- AI-Augmented Engineering Without Outsourcing Judgment
How Claude and Cursor can compress design, coding, and review cycles while keeping architecture and production decisions human-owned.