## What
Regenerates platform documentation version 2.0 from the latest Next
(unreleased) version. This publishes all recent documentation updates
that have been made to the Next version as the stable 2.0 release.
Requested by Ian Alton (@ian-at-airbyte) via Slack thread:
https://airbytehq-team.slack.com/archives/D08FX8EC9L0/p1760747793195139?thread_ts=1760747793.195139
Link to Devin session:
https://app.devin.ai/sessions/edbc303b017445de9731080a55c04586
## How
1. Deleted the existing `version-2.0` directory from
`platform_versioned_docs/`
2. Deleted the `version-2.0-sidebars.json` from
`platform_versioned_sidebars/`
3. Temporarily removed `"2.0"` from `platform_versions.json`
4. Ran `pnpm docusaurus docs:version:platform 2.0` to regenerate version
2.0 from the current Next version
5. Verified the build succeeds locally
## Review guide
1. **New content**:
`platform_versioned_docs/version-2.0/understanding-airbyte/cdc-best-practices.md`
- Comprehensive new CDC configuration best practices guide. Review for
technical accuracy.
2. **Sidebar changes**:
`platform_versioned_sidebars/version-2.0-sidebars.json` - CDC content
reorganized under "Sync Modes" section. Verify navigation makes sense.
3. **Terminology updates** throughout various files:
- "Airbyte Open Source" → "Core"
- "Cloud Teams" → "Cloud Pro"
- "Self-Managed Community" → "Core"
- Verify these align with actual product naming conventions
4. **Content improvements** in access management, API documentation,
connector development, enterprise setup, and quickstart guides
## User Impact
Users viewing the version 2.0 platform documentation will see the latest
content updates, including:
- New comprehensive CDC best practices documentation
- Updated terminology reflecting current product names
- Improved clarity and accuracy throughout documentation
- Better organization of CDC-related content
No negative side effects expected - this is a documentation-only update.
## Can this PR be safely reverted and rolled back?
- [x] YES 💚
This is a documentation change only. Reverting would restore the
previous version 2.0 documentation content.
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io>
Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
## What
Generates version 2.0 of the Airbyte platform documentation using
Docusaurus's built-in versioning system. This creates a frozen snapshot
of the current documentation that users can reference.
Requested by ian.alton@airbyte.io via [Slack
thread](https://airbytehq-team.slack.com/archives/D08FX8EC9L0/p1760490197805979?thread_ts=1760490197.805979).
Link to Devin run:
https://app.devin.ai/sessions/689693593bac44f4903f476aa17b872e
## How
- Ran `pnpm run docusaurus docs:version:platform 2.0` in the docusaurus
directory
- This automatically:
- Created `platform_versioned_docs/version-2.0/` containing a snapshot
of all current platform docs
- Created `platform_versioned_sidebars/version-2.0-sidebars.json` with
the sidebar navigation structure
- Updated `platform_versions.json` to add "2.0" to the version list
- Ran prettier to format the JSON files
- Verified the documentation builds successfully locally (build
completed in ~3 minutes with only pre-existing broken anchor warnings)
## Review guide
1. **Verify timing**: Confirm this is the correct time to release
version 2.0 of the documentation
2. **Version order**: Check `docusaurus/platform_versions.json` - verify
"2.0" is first in the array (newest version first)
3. **Build verification**: Ensure CI/Vercel builds pass without errors
4. **Spot check**: Optionally review 2-3 files in
`docusaurus/platform_versioned_docs/version-2.0/` to ensure content
looks reasonable
Note: This is a standard Docusaurus versioning operation that creates a
frozen snapshot of the current "next" documentation. The generated files
are extensive (500+ files) but follow Docusaurus conventions.
## User Impact
Users will see version 2.0 available in the version dropdown on
docs.airbyte.com. This provides a stable reference point for platform
documentation at this point in time. Existing versions (1.6, 1.7, 1.8)
remain unchanged.
## Can this PR be safely reverted and rolled back?
- [x] YES 💚
This is an additive change that doesn't modify existing versioned docs.
Reverting would simply remove version 2.0 from the version list and
delete the associated documentation files.
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io>
