Alex OS homepage journey engine

A CMS-driven engine that powers the public homepage through two interlocking systems: a journey layer that sequences what visitors see based on context, and an orbit layer that structures how content relationships are rendered. Neither layer is hardcoded — content editors control both through structured CMS fields.

Rather than encoding journey logic in components, Alex pushed that logic into CMS schema. The tradeoff: more upfront schema design work, but the homepage becomes reconfigurable through content alone. This connects directly to the Dynamic CMS Architecture approach Alex uses across projects — structure defined once, reused flexibly.

The orbit layer renders content relationships as navigable clusters rather than flat lists. This required UI/UX Architecture decisions about progressive disclosure — what a visitor sees first, what expands on interaction, and how depth is revealed without overwhelming the initial view.

In progress. The system is tagged as both a build and a thinking project — meaning architectural decisions are still being made alongside active construction. No completion claim is made here; the work is live and ongoing.