canonrs-server 0.1.0

CanonRS server-side rendering support
id: hero_ui
label: Hero UI
family: family-h-layout
category: Display
intent: Semantic UI elements inside HeroBlock
description: Hero typography and label components
composable: false
capabilities: 
required_parts: []
optional_parts: []
tags: ["hero", "title", "subtitle", "description", "heading"]
keywords: 
pain: Hero sections lack consistent structure and semantic grouping
promise: Hero content structured via explicit semantic primitives
why: |
  HeroPrimitive defines a structural block with dedicated parts like title, description and actions. Each part is explicitly declared. This guarantees predictable layout composition.
rules: ["CR-001", "CR-004"]
use_cases: ["landing pages", "marketing headers"]
related: ["card", "resizable", "scroll_area", "aspect_ratio", "page_header", "toolbar", "separator"]
file: hero_ui.css
tokens: hero-*, space-*, font-*
foundation: spacing, typography
states: []
island: hero_boundary.rs
pillar: layout
badges: ["SSR Safe", "Hydration Safe", "Token Driven", "Zero Drift", "Deterministic API"]
before: |
  // ❌ Typical
  view! {
    <div class="hero">
      <h1>"Title"</h1>
    </div>
  }
after: |
  // ✅ CanonRS
  view! {
    <HeroTitle>"Title"</HeroTitle>
  }
boundary_type: passthrough
block: [hero_block]
blocks_primitives: [container, stack, flex]