canonrs-server 0.1.0

CanonRS server-side rendering support
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

id: navigation_menu
label: Navigation Menu
family: family-d-navigation
category: Navigation
intent: Primary site navigation with submenus
description: Navigation menu
composable: true
capabilities: OpenClose
required_parts: ["NavigationMenuList", "NavigationMenuItem"]
optional_parts: ["NavigationMenuTrigger", "NavigationMenuContent", "NavigationMenuLink"]
tags: ["navigation-menu", "navigation", "menu", "nav", "links", "site", "header"]
keywords: 
pain: Nested navigation menus require id wiring and break interaction consistency
promise: Trigger-content relationship enforced without id wiring
why: |
  NavigationMenu uses DOM structure and data-rs-state instead of ids. Trigger and content are linked via closest/sibling logic. This guarantees stable interaction without manual wiring.
rules: ["CR-001", "CR-004"]
use_cases: ["site navigation", "dropdown navigation"]
related: ["sidebar", "nav_item", "breadcrumb", "pagination", "link_group"]
file: navigation_menu_ui.css
tokens: navigation-menu-*, space-*, radius-*, shadow-*, motion-*, font-*
foundation: spacing, radius, shadow, typography, z
states: ["open", "closed", "active"]
island: navigation_menu_boundary.rs
pillar: navigation
badges: ["SSR Safe", "Hydration Safe", "Token Driven", "Deterministic API", "Zero Drift", "Island Architecture"]
before: |
  // ❌ Typical
  view! {
    <button id="trigger">"Menu"</button>
    <div id="content">"Items"</div>
  }
after: |
  // ✅ CanonRS
  view! {
    <NavigationMenu>
      <NavigationMenuItem>
        <NavigationMenuTrigger>"Menu"</NavigationMenuTrigger>
        <NavigationMenuContent>"Items"</NavigationMenuContent>
      </NavigationMenuItem>
    </NavigationMenu>
  }
boundary_type: init
block: []
blocks_primitives: [flex]