Proposals for the next web.
We write focused proposals for the web platform, build the tools that prove them, and move what works toward the standards bodies that can adopt it.
Read the proposals
Draft specifications
Focused proposals for content and application authoring, drafted in the open. Each has its own scope, review, and path into the standards process.
- Declarative HTML ComponentsA markup-first component model with templating, data, reactivity, types, and multi-target lowering.Unofficial Editor's Draft · Stage 0
- HTML FormsA focused proposal for modern request methods, QUERY submissions, and composable submission scopes.Unofficial Editor's Draft · Stage 0
- Opt-in Self-Closing HTMLSelf-closing tags through an explicit document opt-in, with preserved HTML recognition and protected boundaries.Unofficial Editor's Draft · Stage 0
- Flexible HTML NestingPreserve wrappers in constrained HTML contexts and infer native table parts and list items from their composed content.Unofficial Editor's Draft · Stage 0
- HTML Feature ProfilesNamed HTML capability selection and a documented next preset, with fixed resolution and precedence across source, APIs, CSS, and tools.Unofficial Editor's Draft · Stage 0
- Expressive MarkdownA common language for documentation, with readable Markdown, shared semantics and a documented document AST.Unofficial Editor's Draft · Stage 0
Use the tools
Build with it today
JavaScript implementations of the proposals: author a component once as HTML, then run it live, compile it to native DOM, or use it in Vue, React, and Svelte.
Beats Solid, Svelte, Vue, and React in js-framework-benchmark.
npm install @nextwebwg/html-next- Build componentsWrite a reactive component in HTML.
- Use componentsNative DOM, Vue, React, and Svelte setup.
- ConverterGenerate framework source files ahead of time.
- HTML FormsBuild and enhance native form requests.
- Build appsRoutes, layouts, loaders, and static pages with HTMLKit.
About the group
From proposal to platform
Next Web WG is an independent GitHub organization, not a W3C Working Group. Its drafts are proposals: they become web standards only through adoption by the W3C, WHATWG, or another recognized standards venue.
Anyone may participate. Contributions are made under terms that match the W3C Community Contributor License Agreement, so a proposal can move to a W3C group without relicensing. The group is chaired by Matthew Dean; the governance describes how decisions are made and how contributors become editors.