Open navigation
Documentation

Project/Roadmap

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.

ADR-0143 — v0.44 alpha active

0.43.3 remains stable while the compiled OpenElement train begins.

v0.43.3 is the published stable maintenance line. ADR-0143 explicitly opens the 0.44 alpha line for the compiled Element architecture; the Version Plan owns every numbered alpha and the RC gate.

v0.44.0-beta.2CURRENTPublished baseline

The compiled prerelease baseline remains on npm beta; the stable 0.43 line retains latest. Future checkpoint plans are not publication evidence.

prerelease
v0.44.0-beta.2.1NEXTRouter foundation and independent Element

Maintain an upstream-traceable URLPatternList fork and prepare generic contributions; unify route resolution; repair SSG and browser navigation boundaries; qualify standalone Element and prerelease tooling.

planned acceptance checkpoint
v0.44.0-beta.2.2Native and Lit Framework Mode

Use WTR for upstream-aligned browser conformance; prove loader, SSR, client continuation, navigation and actions with Native and Lit; derive a minimal shared protocol and public Document/SEO/search/sitemap metadata; prepare bounded Oxc/TS7 migration experiments. Lit is a support target, not an already-shipped claim.

planned
v0.44.0-beta.2.3Dual-mode qualification

Qualify independent packed consumers, runtime/browser matrices, output and resource cleanup; remove qualified duplicate infrastructure, reconcile documentation and record Alpha migration decisions. No deadline waiver or automatic beta.2.4.

evidence-gated
v1.0.0-alpha.1Public Alpha admission

Start real application use with the public baseline: independently consumable Element and Router with Native/Lit application flows. Actively qualify Oxc/TS7 adoption and platform reductions through subsequent Alpha upgrades; APIs may evolve with migration guidance.

planned
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
  • Preact adapter and Hono API routes via adapter-vite
  • 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 website should read like a Web Standards Lab: dark-first, diagrammatic, useful, and grounded in artifacts users can inspect.

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 adapter-vite
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.