Contributing — Join the lab
BUILD IT with us.
A precise, Deno-first contributor workflow for the Web Standards Lab.
§1 — Setup
git clone https://github.com/open-element/openelement.git
cd openelement
deno install
deno task test
deno task devopenElement core CLI, SSG, serverless API, tests, publishing, and docs site tasks all use Deno 2.9+ as the default runtime. Vite runs via deno run --allow-read --allow-write --allow-env --allow-net --allow-run --allow-sys --allow-ffi --no-prompt npm:vite — no npm or npx needed for the main workflow.
Release line
- Update version numbers (packages/*/deno.json)
- Update the changelog
- Run deno task test
- Publish via deno task --cwd tools/release pack:dry-run, deno task release:check, deno task --cwd tools/release publish:npm
- Create the GitHub Release
§2 — Before a PR
- deno fmt + deno lint stay clean
- Conventional Commits (feat / fix / docs / refactor / test / chore)
- Gates green locally — deno task test before push
- Architectural change? Write the ADR first
Layering discipline: before adding a feature, check whether it can be solved at a lower level — L0 HTML, L1 CSS, L2 Browser API, L3 Hono/Vite/Lit, then L4 custom code.
§3 — Where to help
Lit / FAST / Stencil components that render through our DSD smoke pipeline, with evidence.
Build an application on the stable line and file what breaks. That is the pilot now.
Run the docs gates, fix stale claims, and keep the public surface evidence-backed.