How Rocket works#

Rocket builds websites from Pages. A Page can be a Markdown file for durable content or a JavaScript file for a request-time response. Each Page exports a config object, and config.path controls the public URL.

That means the source file structure is for the author. The URL structure is explicit. You can keep Pages near the content, component, or workflow they document without forcing the same shape into the published site.

What Rocket Needs#

Every Rocket project needs three things:

1. A rocket-config.js file with includeGlobs that tell Rocket where Page files live.
2. One or more .rocket.md or .rocket.js files with an exported config.
3. An npm script that runs the dev server or production build.

The Start With AI page gives a Coding Agent the smallest useful version of that setup. The Manual Quick Start shows the same foundation when you want to create the files yourself.

Learning Path#

Use the docs in this order:

1. Start with Start With AI to have a Coding Agent create a deployable Rocket site.
2. Use Manual Quick Start when you want to create the starter by hand.
3. Continue with Build a Site to add owned site data, layout, menus, assets, and component documentation.
4. Use Component Loading when a page needs custom elements or client-side behavior.
5. Add request-time behavior with Request-time JavaScript Pages.
6. Use Deploy when the site is ready to publish.

Use Reference when you need a specific option or concept. Use Examples when you want a complete implementation pattern.

Before You Start#

The first project usually does not need request-time behavior or a deployment adapter. Those come later, after static Pages build successfully.

Next step#

Continue with Start With AI and create a deployable Rocket site.