URL & slug rules

Slugs are forever. Once an entity ships at a URL, that URL is its permanent identity. Renames create new slugs with 301 redirects from the old slug — never delete the old route, never repurpose it.

Slug rules

• Lowercase only — `flat6labs-cairo-cycle-22` not `Flat6Labs-Cairo-Cycle-22`. Case-sensitive URLs are a 404 hazard.
• Kebab-case — Words separated by hyphens. No underscores, no camelCase, no spaces, no special characters except hyphen.
• Latin script only — Even for AR content. Slugs are URL identifiers, not editorial titles — they stay Latin to remain stable across both locales and to survive copy-paste from URL bars.
• Descriptive, not opaque — `/founder-files/before-you-ask-for-funding` not `/founder-files/ff-01`. The slug carries SEO signal.
• Stable forever — Once published, slugs do not change. If editorial demands a rename, a new slug is created and the old slug serves a 301 to the new one in perpetuity.

URL structure summary

/{locale}/{module}/{slug} — e.g. /en/founder-files/before-you-ask-for-funding. Nested patterns for Calendar: /{locale}/calendar/events/{slug}. Sub-pages on the same entity: /{locale}/{module}/{slug}/{sub} (only the Founder File reader uses this pattern).