Lessons from combining Google Sheets, Apps Script, and modern frontend UX

Why I still use Sheets for selected products

For fast-moving product environments, Google Sheets can be an excellent operational CMS layer. Non-technical collaborators can update content immediately, and engineering can keep the rendering layer strongly typed.

The architecture that worked

In this portfolio stack, I use:

• Local static core data for identity and positioning
• CMS-driven dynamic records for projects, posts, journey, and studies
• Parser utilities that normalize sheet rows into typed models

This hybrid approach keeps stable brand messaging in code while preserving editing speed for content-rich sections.

What to watch out for

• Keep schema expectations explicit.
• Parse booleans, arrays, and slugs defensively.
• Always ship fallback content for resilience.

Closing

The goal is not to avoid real backends forever. The goal is to ship maintainable systems that meet current product constraints.