Shane design and UX taste

The Shanepedia corpus already points toward a clear taste profile: simple sites that boot instantly, low-friction navigation, obvious next steps, and interfaces that feel intentional instead of corporate. The local site should communicate founder clarity, not generic note-taking software.

Strong defaults

• editorial rather than dashboard-heavy
• fast, readable, mobile-aware layouts
• clear hierarchy and strong section labels
• obvious search and browse paths
• copy that sounds direct, specific, and confident
• visual warmth instead of cold SaaS neutrality
• a founder/operator tone that feels calm, sharp, and practical

Concrete site rules

• make the current page obvious in navigation
• show enough search context that a user can choose before clicking
• use typography with more contrast between page title, section title, and body
• keep touch targets generous on mobile
• make search feel like a primary control, not an afterthought
• avoid UI chrome that competes with the content

What to avoid

• overloaded nav trees
• generic startup gradients with no point of view
• slow or decorative UI that delays useful action
• vague feature language instead of real outcomes

UX implication for Shanepedia

The site should feel like:

• a founder field notebook
• a research terminal with taste
• a place where ideas turn into projects, not just documents

More specifically, it should communicate direct, high-signal minimalism: fast boot, low chrome, obvious utility, and just enough visual identity to feel intentional rather than generic.