Launch docs and external readiness

Problem

External users cannot adopt connector dashboard packs without documentation that explains how to install a pack for their Fivetran source, what each dashboard shows, how KPIs are defined, and how to customize or extend packs for their schema. Currently, all knowledge about pack usage lives in internal team context and ad hoc docs from the pilot phase. Without publishable, executable documentation—including quickstart guides, example dashboards, and troubleshooting steps—new users will fail at onboarding and the support burden will be unsustainable at public launch scale.

Context

• Even if connector-specific dashboard packs and KPI narratives for Fivetran sources 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 dashboard pack YAML, dbt/example assets, connector fixtures, and quickstart docs, 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 connector-specific dashboard packs and KPI narratives for Fivetran sources 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