Roadmap

OpenElement roadmap labels describe the public product surface, tied to package truth, docs truth and CI evidence rather than a wish list.

01 / release line

From shipped evidence to v1.0 freeze.

The line is deliberately narrow: only claims that can survive docs, package exports and build validation stay visible.

Alpha baseline — v1.0.0-alpha.1

0.43.3 remains stable while the 1.0 Alpha baseline lands.

element v0.43.3 · create v0.43.3 · ui v0.43.3 · router v0.41.0-alpha.6 is the published stable maintenance line. 1.0 Alpha is the new baseline: Element and Router as the public core, Create as the supported entry, UI as experimental — with no supported migration from 0.x.

v1.0.0-alpha.1BASELINEPublic Alpha admission

Start real application use with the public baseline: independently consumable Element and Router with Native/Lit application flows. Element and Router are the public core, Create is the supported entry, UI is experimental. 1.0 Alpha is a fresh baseline with no supported migration from 0.x.

published to npm under the @alpha dist-tag

v1.0 RC / StableSeparately admitted releases

Freeze contracts and dependencies after Alpha evidence; require at least fourteen days of RC soak, install/upgrade/security qualification and human GO. Element and Router do not mandate a package count.

unscheduled

02 / product boundary

Scope is explicit.

Current capability, excluded promises and the visual contract are kept separate.

in product

In product

JSX-first application API
Declarative Shadow DOM rendering
Routes, layouts, content, islands, and i18n
Loaders and actions with progressive-enhancement forms
CSRF floor on the action surface
Nitro server output (Node + Workers) and SPA mode
Locale-prefixed routing with Document and head ownership
Verified package and release boundaries

out of current scope

Out of current scope

Hub product language
Registry Hub as a current product promise
RPC, CEM, and interop adapter package promises
Generic auth, ORM, or database platform claims
Old package-count public graph language

design rule

Design rule

The public site is a working demonstration of the framework’s static-first output.

03 / decision matrix

Roadmap language stays inside the product boundary.

Ship, prove and freeze are evidence states rather than marketing labels.

ShipOnly public contracts reflected in docs, generated pages, and package surfaces.

ProveUse CI, build checks, and docs scans as release evidence before expanding claims.

FreezeMove toward v1.0 after the WC fullstack framework and Basic Element line is stable, readable, and boring to verify.

04 / system visual

The package graph is part of the release artifact.

Published package ownership and the public architecture must remain mechanically identical.

package matrixproduct boundary

Elementscustom elements, DSD rendering, and component contracts

UIOpen Props primitives used by this website and consumers

Frameworkroutes, layouts, content, islands, i18n, and router build

Protocolspublic boundary declarations and package compatibility language

release disciplinev1.0 posture

No driftMarketing language, docs, package exports, and CI gates must agree.
No ghostsArchived Hub-era promises and No webpack-era shortcuts stay out of the current public product line.
No fogUsers should understand what is shipped, current, planned, and explicitly out of scope.