openElement docs are organized like an engineering workspace: build paths, API surface, architecture decisions, and release truth sit next to each other.
command palettedocs nav
reference desk
route/guide/getting-started
api/apilist
graph/architecture/architecture
route graphfast paths
/homepage lab artifact and product paths
/guide/*build path, configuration, deployment, and production flow
/architecture/*package graph, DSD, islands, and standards registry
/apipublic contract index across the product graph
usage workflowdocs as product
How to use this site
BuildStart with the guide when the question is how to ship a page.
VerifyUse API and architecture pages for contract-level precision.
DecideUse roadmap and changelog pages to avoid stale assumptions.
ContributeRead architecture before changing package boundaries.