01
Fullstack framework
Routes, layouts, islands, API paths, assets, deploy targets, and desktop targets owned by OpenElement contracts.
Standards become an interface
The app model and element model share one contract.
openElement is presented as a standards-first WC fullstack surface: native components, generated route metadata, DSD output, and package boundaries stay inspectable. Dogfood apps validate the framework contract; governance gates protect releases.
02
Basic Element
A small native Web Components authoring layer with shadow/DSD default output and explicit light DOM opt-in.
03
Official stack
Protocols, UI, Vite, Hono, Nitro, Deno Desktop, Preact islands, and third-party WC compatibility support the two products.
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: