Navigation Structure
Public navigation
Public navigation — documentation pending.
Complete
Public navigation is what an unauthenticated visitor sees on every page — header chrome + footer columns + breadcrumb on detail pages. It is the same on Home as it is on a deep founder profile. Predictable.
Three surfaces, one contract
- Header
- Sticky on scroll. 9 main nav items + utility bar (desktop) / hamburger drawer (mobile). See Section 3.
- Footer
- 4-column utility links + brand row + subscribe + legal. Compact modifier applied platform-wide.
- Breadcrumb
- Detail pages only. Above the title, below the header. See "Breadcrumb rules" topic.
URL structure for public routes
- Locale prefix is always present. — Every public URL starts with `/:lang/` where lang is `en` | `ar`. There is no rootless URL — a bare `/foo` would 404.
- Module-then-entity. — Detail pages live at `/:lang/<module>/<slug>`. Example: `/en/founder-files/before-you-ask-for-funding`.
- Calendar uses nested paths. — Events live at `/:lang/calendar/events/<slug>`. Country / category / audience pages live one level deeper.
- Slugs are URL-stable. — Once an entity ships, its slug never changes. Renames create new slugs with 301 redirects from the old slug.
