Build on the platform.
Version-matched guides for browser applications, universal rendering, tooling, and deployment.
Support matrix · Package portal
First framework project? Use the junior learning path for a progressive feature and plain-language glossary.
import { createApp, html } from '@gluonjs/core';
import { ref } from '@gluonjs/reactivity';
const count = ref(2);
createApp(() => html`
<main>
<h1>Count ${count.value}</h1>
<button type="button" @click=${() => { count.value += 1; }}>Increment</button>
</main>
`).mount(document.querySelector('#app')!);
Guides
Step-by-step paths for browser applications, universal rendering, tooling, and production deployment.
Component libraries
Gluon 1.2 adds a public Quarks manifest and loader contract for separately packaged component libraries. Consumers request declared entries explicitly, retain observable loading and cache state, and own Custom Element registration, constructable stylesheets, SSR style snapshots, and disposal. The maintained package consumer and Storybook catalog exercise those same public boundaries.
Choose Atom, Molecule, Organism, or Custom Element →
Interactive graph
Explore a real, native-control knowledge map built with the optional
@gluonjs/graph Custom Element.
Schema-driven forms
The optional @gluonjs/json-forms package renders its documented JSON Schema
and JSON Forms UI-schema subset through form-associated, accessible native
controls. Its delivery-preferences reference flow keeps the policy state in the
host application and the component responsible for rendering and validation.
Request-free forms
For application-owned forms, @gluonjs/molecules provides a DOM-independent
controller for typed field state, async validation, submission lifecycle, and
SSR snapshots while native controls remain the rendering boundary.
API reference
Generated, version-matched API documentation for every current public package entry point.
Cookbook
Compiled recipes for common application, component, routing, state, rendering, and testing work.
Migration
Manual Vue-to-Gluon concept mapping, a tested reversible cutover playbook, and release-to-release upgrade policy, with the supported automation boundary stated explicitly.