Navigation Philosophy — Wordmark Only, Transparent Hub
A nav rail implies sections worth navigating. The hub has none — it is one page. Nav rail on a one-page site is organizational noise that implies complexity that doesn't exist. The decision: wordmark only, no nav rail. Subline below the wordmark carries descriptive context in one line (title, key affiliations as clickable links) without navigation overhead. The hub's call to action is to leave for a spoke, not to navigate within the hub. Footer handles links and attribution.
Capture
A hub with a full navigation rail is a hub that behaves like a content site. A hub with a wordmark and nothing else is transparent: it steps out of the way and sends the visitor outward. The decision: wordmark only, no nav rail, no section tabs, no sidebar links.
The wordmark establishes identity and provides a home link. A subline below the wordmark carries descriptive context — title, key affiliations — without requiring navigation. The footer handles links and attribution. Between the wordmark and the footer, the landing page is the entire experience.
Why
A nav rail implies there are sections worth navigating within the hub. The hub has no content sections — it is a single landing page. A nav rail on a one-page site is organizational noise. It implies complexity that doesn't exist. It creates a visual affordance that suggests the visitor can go somewhere within the hub when all the real destinations are in the card grid, which points outward.
The transparent hub has a clear call to action: leave and go somewhere interesting. Every design element that competes with that call to action — nav rails, sidebar links, footer sections with internal links — dilutes the signal.
The subline below the wordmark does real work without navigation weight. "Systems Architect · YY Method · BenChanViolin" tells the visitor who this person is in one line. It carries credential signals — the kind that build trust — without requiring the visitor to navigate anywhere to understand them. Two of the three items in the subline are clickable, pointing to the methodology site and the YouTube channel. This is navigation embedded in context, not navigation abstracted into a separate structure.
Why-Not
Why not add a nav link to /about? The about section is folded into the landing page (C6-008). There is no separate /about to link to. If a future decision creates a standalone /about page, a nav link becomes appropriate.
Why not add nav links to the spokes? The card grid is the navigation structure for the spokes. Adding spoke links to the nav rail creates two navigation paths to the same destinations — one contextual (cards with descriptions), one bare (nav links with labels). The card grid is the better navigation element because it carries context. The nav rail would be redundant and would compete with the cards for visual attention.
Why not add social links to the nav? Social links are outbound, not inbound. They belong in the footer or as part of the about section. Nav real estate is for intra-site navigation. This hub does not have enough intra-site navigation to justify a nav rail; it should not use nav space for outbound links.
Commit
Decision: Hub navigation is wordmark only. Subline carries descriptive context in one line. Footer handles links and meta. No nav rail. The call to action on the hub is to leave, not to stay.
Confidence: High. The minimal navigation posture is consistent with the hub's transparent role and zero-content architecture.
Timestamp
2026-04-05