Launch docs and external readiness

Problem

There is no external-facing documentation for the Cloud Suite's collaboration and sharing features. New users arriving at launch will have no guides, examples, or quickstart material to help them connect a project, set up a workspace, invite collaborators, or publish dashboards. Without executable documentation — content that a new user can follow step-by-step and get a working result — the onboarding experience depends entirely on the UI being self-explanatory, which it is not yet.

Context

• Even if hosted onboarding, collaboration, and account/project workspace UX works, launch will still fail if external users and operators cannot understand setup, limits, and expected behavior from publishable docs.
• This task is about making the product externally explainable: clear setup guidance, examples, troubleshooting, and boundary-setting around what is and is not supported at launch.
• Expected touchpoints include apps/cloud/, templates/browser flows, auth/account docs, and cloud tests, user-facing docs, operator notes, and any examples or screenshots needed to make the launch story concrete.

Possible Solutions

• A - Ship with only internal notes and ad hoc examples: faster, but it shifts launch confusion onto support and sales conversations.
• B - Recommended: produce a focused external-readiness doc set: cover setup, primary workflows, limitations, troubleshooting, and operator/admin guidance where needed.
• C - Delay docs until after launch traffic appears: saves time now, but increases launch-day friction and inconsistent messaging.

Plan

1. Define the minimum documentation set needed for external users, internal operators, and anyone supporting hosted onboarding, collaboration, and account/project workspace UX at launch.
2. Draft or update the core guides, examples, known-limits sections, and troubleshooting notes using the actual launch scope.
3. Review the docs against the product behavior and remove any claims that are not yet supportable in the code or operations model.
4. Link the publishable docs to follow-up maintenance owners so launch documentation does not drift immediately after release.

Implementation Progress

Review Feedback

• [ ] Review cleared