Rocket is currently in public alpha. This roadmap describes the work that keeps the public alpha
credible and the criteria for a future 1.0.0.
- Keep the public positioning focused on AI-generated, owned static sites and Web Component docs.
- Keep README, docs, npm package metadata, and release notes aligned on
@rocket/js. - Treat npm as the
@rocket/jsrelease channel, not a separate launch status. - Continue publishing with npm provenance from GitHub Actions.
- Maintain
SECURITY.md,CHANGELOG.md,CONTRIBUTING.md, and a committed lockfile. - Surface one polished marketing-site example, one component-library docs example, and one AI-generated-from-brief example.
- Stabilize Page config, layout, component registration, and asset APIs.
- Document the breaking-change policy with examples from alpha releases.
- Decide whether Rocket needs an official project scaffolder.
- Keep examples pinned to the current package version.
- Add migration notes for any alpha API changes.
- Rocket will not become a SPA framework.
- Rocket will not become a backend application framework.
- Rocket will not try to match the plugin ecosystems of Astro, Eleventy, or VitePress.