Learn by building
Generate a working application first, then add components, state, routing, and deployment only when the product calls for them.
Follow the learning path
Start with a working app, add only the capabilities you need, and keep every boundary public and inspectable.
Gluon builds on the browser platform instead of hiding it. Its packages make rendering, reactive state, application ownership, and native Custom Elements compose without turning each capability into a private framework convention.
npm create gluon@latest my-app and choose only the capabilities your application needs.| You want to… | Start here |
|---|---|
| Create a working project | Getting started |
| Understand the model step by step | Learning path |
| Build one stateful component | First component |
| Pick a package | Package guide |
| Combine Router and Store | Application architecture |
| Render and hydrate on the server | Universal rendering |
| Load component data during SSR | Async data and SSR |
| Find an API contract | API reference |
| Move from Vue | Migration guides |
The examples use official public package entry points. The living GLUON GOODS shop remains the application acceptance surface wherever a feature has a real customer flow.