sboghossian Feature Router — Site Navigation
Purpose
Route any inbound feature slug — from URL path, site search, or in-app navigation — to the correct product feature explanation page. This is the general-purpose feature routing handler. Specialized sub-routers handle specific domains:
- AI skills and tools → [[site-ai-feature-router]]
- Contract clauses → [[site-clause-router]]
- Document library → [[site-legal-document-router]]
- Persona/solution pages → [[site-solutions-router]]
Inputs / signals
| Signal | Examples |
|---|---|
| Direct URL path | /features/contract-review, /features/nda-drafting, /features/clause-library |
| Site search — feature keyword | "contract review", "draft NDA", "employment agreement generator" |
| In-app deep-link | From within the product, link to a feature explanation page |
| Marketing link | From email, ads, social — /features/[slug]?utm_source=... |
Logic
1. Receive: feature slug from URL path OR parsed feature keyword from search.
2. Look up slug in feature registry:
a. Exact slug match → route to /features/[slug]
b. Keyword match → route to best-matching feature page
c. Category match → route to /features (category filtered)
d. No match → fall back to site search results
3. Render feature page:
- Feature name + one-paragraph description
- Screenshot or embedded demo
- Jurisdiction and practice-area tags
- "Try in Louis" CTA
- Related features (2–3)
4. Track feature page view for analytics.
Feature page content requirements
Each /features/[slug] page must include:
- Feature name: clear, plain-language (e.g., "Contract Risk Review", not "ML-Powered Document Analyzer").
- One-paragraph description: what it does, for whom, in what jurisdictions.
- Screenshot or demo: visual proof of what the output looks like.
- Jurisdiction tags: which jurisdictions are covered (especially MENA-specific features).
- Practice area tags: M&A, employment, commercial, etc.
- CTA: "Try this feature" or "Start free" depending on the user's auth state.
- Related features: 2–3 links to related feature pages.
URL convention
/features/[category]/[slug] — for categorized features
/features/[slug] — for top-level features
/tools/[slug] — for standalone calculators and tools
Why this matters
Feature pages serve two audiences:
- Discovery: site visitors who don't yet know the platform's full capability set — feature pages make capabilities tangible.
- Re-engagement: existing users who want to deepen their use — feature pages surface capabilities they haven't tried yet.
A clean, fast feature-page routing layer is essential for both SEO (feature pages rank for "[tool type] legal AI" searches) and product-led growth (self-serve discovery of new capabilities).
Related skills
- [[site-ai-feature-router]] — specialized routing for AI skill and calculator queries
- [[site-clause-router]] — routing for clause-specific queries
- [[site-legal-document-router]] — routing for document-library queries
- [[site-solutions-router]] — persona-based routing
- [[site-compare-us-router]] — competitor comparison routing