This roadmap tracks ecosystem-level priorities across CLI, IDE, Core, and Examples.
- Establish central hub documentation and identity
- Standardize repository messaging as one platform
- Enforce cross-repo badge and discoverability links
- Align release quality gates for credibility
Success signals:
- All primary repos link back to this hub
- All primary repos expose clear role/ownership in README
- Public architecture story is consistent across repos
- Evolve
rapidkit-examplesinto reference architectures - Publish scenario-first examples (API, microservice, polyglot, enterprise)
- Add end-to-end getting-started tracks from CLI to deployed app
Success signals:
- Faster time-to-first-success for new users
- Improved conversion from star to clone to run
- Higher external shareability of example projects
- Harden drift prevention and contract testing across repos
- Strengthen multi-OS confidence for CLI and IDE paths
- Add explicit compatibility matrix and support policy
Success signals:
- Lower regression rate across releases
- Predictable upgrades with fewer manual fixes
- Reduced support load for common setup issues
- Clarify contribution lanes by repository
- Add high-quality “good first issue” tracks
- Improve maintainer response templates and triage process
Success signals:
- More external PRs reaching merge quality
- Shorter cycle time from issue to resolution
- Better contributor retention
- Expand official integrations and templates
- Publish advanced guides for teams and organizations
- Strengthen platform narrative in releases and changelogs
Success signals:
- Broader repository engagement across the ecosystem
- Higher trust in production adoption
- Stronger long-term community growth