Give readers a version.
Publish reviewed docs for your organization or the public. Each version has its own address, so readers can return to the release they use.
RDYHUB / IN DEVELOPMENT
Publish.
Collaborate.
Work across projects.
rdy on your machine.
rdyhub across your team’s work.
Keep working locally in rdy. Publish versions for readers, review changes with teammates, and follow your projects over time.
What rdyhub addsWHAT RDYHUB ADDS
From local work
to shared projects.
rdy keeps docs and decisions consistent on your machine. rdyhub adds publishing, team workflows, and a view across projects.
Work from one agreed design.
Share a project across people and machines. Review changes before they join the shared design, under rules your team sets.
Follow the work over time.
See trends and review activity across projects. Use dashboards, alerts, and scheduled reviews to keep track of what needs attention.
HOW THE WORK FITS TOGETHER
Agree on the change.
Publish it. Follow it.
Your team changes a policy used by several projects. The design needs agreement, readers need updated guidance, and the team needs to follow the work across projects.
- COLLABORATE
Review the change.
Work locally in rdy, then review what joins the team’s shared design.
- PUBLISH
Give readers the update.
Review what the new version shares, choose its audience, and publish it.
- ACROSS PROJECTS
Keep track of the work.
Use cross-project views and trends to see where reviews and updates need attention.
IN DEVELOPMENT
Starting with publishing.
The first beta focuses on publishing reviewed versions for readers. Shared project workflows, cross-project views, and code checks are planned for later releases.
rdy still works on its own.
Write, review, approve, and read your docs locally. No rdyhub account required.