Rocket
On this page

Build the Static Site#

The Acme UI Docs project now has Pages, user-owned site data, a docs layout wrapper, menu structure, Site Head Metadata, brand assets, and the first documented component.

Run the production build#

npm run build

Rocket writes the static output to dist/.

Inspect the output#

Check that the important Pages exist:

ls dist
ls dist/components/button
ls dist/brand

Then preview the built files with any static file server. For example:

npx --yes http-server dist

Visit these paths in the preview server:

Final project shape#

Your project should now look like this:

acme-ui-docs/
├── package.json
├── rocket-config.js
├── public/
│   └── favicon.svg
├── docs/
│   ├── assets/
│   │   ├── acme-mark.svg
│   │   └── acme-wordmark.svg
│   ├── docsLayout.js
│   ├── pages/
│   │   ├── brand.rocket.md
│   │   ├── components/
│   │   │   └── index.rocket.md
│   │   ├── getting-started.rocket.md
│   │   └── index.rocket.md
│   └── siteData.js
├── src/
│   └── components/
│       ├── AcmeButton.js
│       └── AcmeButton.rocket.md
└── .agents/
    └── skills/
        └── rocket/
            └── SKILL.md

The .agents/skills/rocket/SKILL.md file is created by rocket init. Keep it if you use a coding agent on the project; remove it if you do not need project-local agent instructions.

Where to go next#

Checkpoint#

The static-site chapter ends with complete static documentation output. Every file under src/ is owned by the Acme UI Docs project, every file under docs/ is owned by the Acme UI Docs documentation site, and Rocket supplies the build pipeline plus the reusable Atlas docs layout.