01
Elements
Author encapsulated, interoperable components. Rendered natively. Composed by design.
Standards become an interface
Elements, routes, and protocols share one contract.
openElement is presented as a standards-first product surface: native components, generated route metadata, DSD output, and package boundaries are designed to stay inspectable.
02
Routes
File-based routing with data, streaming, and progressive enhancement built in.
03
Protocols
Package and ship UI, data, and logic with open, layerable protocols.
System model
DOM tree, route graph, island hydration, package graph.
The page language uses real project boundaries: route metadata from the app, DSD as render output, hydrated islands for interaction, and package contracts as the reference surface.
deno run -A npm:@openelement/create my-app deno task dev deno task build<open-layout>
<docs-home></docs-home>
</open-layout>Developer workflow
Create, compose, route, render, hydrate, ship.
The homepage middle section is no longer a sparse card strip. It explains the actual work path a developer follows through the framework.
Reference surfaces
Follow the docs, API, and roadmap truth.
The site keeps content grounded in generated routes, package surfaces, and current roadmap anchors instead of invented marketing copy.
Island hydration smoke line
Native components stay inspectable.
The same composed surface hydrates as a real custom element, with shadow DOM boundaries and signal updates preserved after static generation.
LIVE VERIFICATION CONSOLE
METRICS packages verified: