• Sns.Admin
  • /docs/ux/navigation
  • Docs
    • Overview
      • Approach
      • Vision
    • Concepts
      • Communities
      • Places
      • Structures
      • Spaces
      • Assets
    • Platform
      • Architecture
      • Sns.Framework
      • Sns.Spatial
      • Data Model
    • UX Patterns
      • Entity Icons
      • Editors
      • Layouts
      • Navigation
    • Workflows
      • Place Onboarding
      • Asset Uploads
      • Requests
      • Projects
    • Spatial
      • Maps
      • Providers
      • Geo DTOs
      • Digital Twins
    • Data
      • Places
      • Assets
      • NavItems
      • Scoring
    • AI / Automation
      • AI Assistants
      • Completeness
      • Confidence
      • Monitoring
    • Developer Guide
      • Getting Started
      • Repo Map
      • State Patterns
      • Coding Standards

New Page

docs/ux/navigation

Navigation

Navigation in SnS combines database-backed application navigation with local technical documentation trees where the content is still being shaped. DatState owns global navigation resolution and exposes valid sitemap items based on configured routes.

Patterns

  • Use database NavItems for application navigation when routes are managed by the platform.
  • Use local navigation structures for temporary documentation trees until a DocState pattern is approved.
  • Use NavLink for route-aware active behavior when rendering links in Razor.
  • Keep active-class helpers simple and local to the state or component that owns the selection.

Boundary

SnS and DataMine documentation libraries currently use different layouts. Cross-library switching should happen from deliberate outer navigation rather than inside one library layout.

More info goes here.
  • Home
  • Finder
  • This Place
  • Explore
  • Database
  • Solutions
  • Ready
  • : 1
  • Enterprise: 13
  • Application: 1046
  • NavItem:
  • Theme: 1