User Guide
Raydo Desktop workflows and product behavior.
The User Guide explains Raydo Desktop from the perspective of someone trying to get work done.
Write from the product, not the code
User-facing pages should name what the user sees, what decision they need to make, and what outcome they can expect.
Main areas
Chat
Start work, choose context, inspect progress, and review output.
Projects
Keep tasks, files, previews, and deliverables together.
App Connections
Connect providers, apps, and services with clear boundaries.
Deliverables
Preview, export, and trace generated work.
Raydo CLI
Use command-line checks, operations, provider auth, scheduled tasks, and support bundles.
Product language
Organization is the work context.
Role describes who is doing the work.
Capability describes what Raydo can use.
Flow describes repeatable work.
Page quality bar
A good user guide page includes:
- one concrete workflow;
- the visible UI names a user will see;
- success and failure states;
- privacy or safety notes when context or automation is involved.