portal-onboard

To publish a client portal for the first time, use a sequential onboarding wizard that verifies local readiness, creates a draft from templates or transcripts, previews locally, and deploys to the cloud. This guided workflow removes setup friction and tracks progress through checkpoints.

Yes, you can create a portal draft directly from a meeting transcript, brief description, or template. The onboarding workflow uses your input content to generate the portal structure, suggests a slug, and applies soft-retry logic to resolve any naming conflicts automatically.

The best way to preview a portal locally is through an onboarding flow that runs local dev-server checks and handles credentials before invoking the preview process. This ensures your environment is fully validated and ready prior to executing the cloud deployment.

Yes, the portal onboarding process resumes if interrupted because it uses telemetry logging and checkpointed progress. This allows the sequential wizard to recover your workflow state and continue from the last successful local validation or deployment step.

No, you do not need to manage cloud credentials separately when deploying a portal because the onboarding workflow includes inline credential handling. The wizard directly manages authentication as part of the sequential publish flow to cloud infrastructure.

You should use a guided wizard instead of manually configuring a portal workspace to avoid environment setup errors and ensure schema validation. The wizard orchestrates end-to-end creation, preview, and deployment, applying telemetry for immediate recovery from any local readiness failures.