Skip to content

P4: Production onboarding, marketplace readiness, and public documentation #104

Description

@iamfatness

Problem

A published app must be understandable to external users without exposing internal credential setup or overpromising Sidecar capabilities.

Outcomes

  • Docs match current product UI and capabilities.
  • Marketplace/OAuth/Public Client setup is documented for publisher operations, not end-user setup.
  • Website, README, release notes, installer, and screenshots stay synchronized.

Acceptance criteria

  • Fresh user can install, sign in, join, assign sources, record ISO, and collect diagnostics from docs alone.
  • Sidecar docs are gated until Sidecar is production-ready.
  • Website deployment is part of release checklist.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:docsUser docs, operator guides, marketplace readinesspriority:P3Longer-term scale/commercial polishtype:featureNew product capability

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions