Docs plus plan (#68154)

Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: ian-at-airbyte

docs/community/contributing-to-airbyte/writing-docs.md

@@ -148,7 +148,7 @@ The [Good Docs Project](https://www.thegooddocsproject.dev/) maintains a collect
 | --------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
 | Concept         | Explain a concept, context, or background information about a product or its features.              | [Template](https://gitlab.com/tgdp/templates/-/tree/main/concept)         |
 | How-to          | A concise set of numbered steps to do one task with the product.                                    | [Template](https://gitlab.com/tgdp/templates/-/tree/main/how-to)          |
-| Tutorial        | Instructions to set up an example project intended for hands-on learning.        | [Template](https://gitlab.com/tgdp/templates/-/tree/main/tutorial)        |
+| Tutorial        | Instructions to set up an example project intended for hands-on learning.                           | [Template](https://gitlab.com/tgdp/templates/-/tree/main/tutorial)        |
 | Troubleshooting | Common problems experienced by users, an explanation of the causes, and steps to resolve the issue. | [Template](https://gitlab.com/tgdp/templates/-/tree/main/troubleshooting) |
 | Reference       | Specific, in-depth details about a particular topic.                                                | [Template](https://gitlab.com/tgdp/templates/-/tree/main/reference)       |
 | Release note    | Communicate new features, improvements, bug fixes, and known issues about a product.                | [Template](https://gitlab.com/tgdp/templates/-/tree/main/release-notes)   |
@@ -218,22 +218,22 @@ Certain Airbyte products reserve some platform features. To avoid confusion and
 
 To enable badges, include `products` in the Markdown metadata. The following values are possible, and you can combine them as needed.
 
-**Badge display:** all 5 badges always appear in order - Core, Standard, Pro, Enterprise Flex, Self-Managed Enterprise. Available badges appear highlighted, unavailable badges appear grayed out.
+**Badge display:** all 6 badges always appear in order - Core, Standard, Plus, Pro, Enterprise Flex, Self-Managed Enterprise. Available badges appear highlighted, unavailable badges appear grayed out.
 
 **Metadata keys:**
 
-- `all`: Core, Self-Managed Enterprise, and Standard - doesn't include Pro, Enterprise Flex, or Embedded
+- `all`: Core, Self-Managed Enterprise, Standard, and Plus - doesn't include Pro, Enterprise Flex, or Embedded
 - `oss-community`: Core only
 - `oss-enterprise`: Self-Managed Enterprise only
-- `cloud`: Standard only (also enables Pro and Enterprise Flex due to Cloud tier inheritance)
+- `cloud`: Standard and Plus (also enables Pro and Enterprise Flex due to Cloud tier inheritance)
 - `cloud-teams`: Pro only (also enables Enterprise Flex due to Cloud tier inheritance)
 - `enterprise-flex`: Enterprise Flex only
 - `embedded`: Embedded only (hidden if not specified - there is no off state for the Embedded badge)
 
 **Cloud tier inheritance:** higher Cloud plans automatically inherit availability from lower tiers:
 
-- If you specify `cloud`: Standard, Pro, and Enterprise Flex badges all become enabled
-- If you specify `cloud-teams`: Pro and Enterprise Flex badges become enabled - Standard turns off
+- If you specify `cloud`: Standard, Plus, Pro, and Enterprise Flex badges all become enabled
+- If you specify `cloud-teams`: Pro and Enterprise Flex badges become enabled - Standard and Plus turn off
 - If you specify `enterprise-flex`: Only Enterprise Flex badge becomes enabled
 
 **Self-managed plans** Core and Self-Managed Enterprise don't inherit from each other.
@@ -250,7 +250,7 @@ products: oss-community
 Some text.
 ```
 
-In this example, Pro, and Enterprise Flex badges appear highlighted due to Cloud tier inheritance, while Core, Standard, and Self-Managed Enterprise badges appear grayed out.
+In this example, Pro, and Enterprise Flex badges appear highlighted due to Cloud tier inheritance, while Core, Standard, Plus, and Self-Managed Enterprise badges appear grayed out.
 
 ```markdown
 ---
@@ -408,18 +408,17 @@ You can run Vale in a command line tool or you can install an extension for most
    ```
 
 2. Lint your content. You can lint a single file or an entire directory and its subdirectories.
-
    - To lint a file, type the relative path to the file.
 
-      ```bash
-      vale ../docs/myfolder/myfile.md
-      ```
+     ```bash
+     vale ../docs/myfolder/myfile.md
+     ```
 
    - To lint a folder, type the relative path to that folder and end with a slash.
 
-      ```bash
-      vale ../docs/myfolder/
-      ```
+     ```bash
+     vale ../docs/myfolder/
+     ```
 
    - For more command-line tool help, see [Vale's docs](https://vale.sh/docs/cli).
 
@@ -445,29 +444,29 @@ brew install markdownlint-cli2
 
 To lint files:
 
-   - To lint a single file:
+- To lint a single file:
 
-      ```bash
-      markdownlint-cli2 "./docs/myfolder/myfile.md"
-      ```
+  ```bash
+  markdownlint-cli2 "./docs/myfolder/myfile.md"
+  ```
 
-   - To lint a single directory but not its subdirectories:
+- To lint a single directory but not its subdirectories:
 
-      ```bash
-      markdownlint-cli2 "./docs/myfolder/*.md"
-      ```
+  ```bash
+  markdownlint-cli2 "./docs/myfolder/*.md"
+  ```
 
-   - To lint a directory and its subdirectories recursively:
+- To lint a directory and its subdirectories recursively:
 
-      ```bash
-      markdownlint-cli2 "./docs/folder/**/*.md"
-      ```
+  ```bash
+  markdownlint-cli2 "./docs/folder/**/*.md"
+  ```
 
-   - To auto-fix issues, add a `--fix` modifier. MarkDownLint can fix most issues on its own, but it might not fix them all.
+- To auto-fix issues, add a `--fix` modifier. MarkDownLint can fix most issues on its own, but it might not fix them all.
 
-      ```bash
-      markdownlint-cli2 --fix "../docs/myfolder/*.md"
-      ```
+  ```bash
+  markdownlint-cli2 --fix "../docs/myfolder/*.md"
+  ```
 
 For full usage details, see the tool's [GitHub readme](https://github.com/DavidAnson/markdownlint-cli2?tab=readme-ov-file#use).
 
@@ -525,19 +524,17 @@ When you release a new major version of Airbyte like 2.0 or 2.1, generate a docu
 
 2. Open a terminal, change to the docusaurus folder, and run the command to generate a version. `<version>` can be a number like `2.0` or anything else you like. Be consistent with Airbyte and other versions on the docs site. Whatever string you enter here later appears in the docs UI.
 
-      ```bash
-      cd docusaurus
-      pnpm run docusaurus docs:version:platform <version>
-      ```
-
-      Docusaurus automatically does three things at this point. It:
+   ```bash
+   cd docusaurus
+   pnpm run docusaurus docs:version:platform <version>
+   ```
 
-      - Defines the existence of that version in the `/docusaurus/platform_versions.json` file
-      - Creates a physical copy of the versioned platform docs in `/docusaurus/platform_versioned_docs`
-      - Creates a physical copy of the versioned platform sidebar in `/docusaurus/platform_versioned_sidebars`
+   Docusaurus automatically does three things at this point. It:
+   - Defines the existence of that version in the `/docusaurus/platform_versions.json` file
+   - Creates a physical copy of the versioned platform docs in `/docusaurus/platform_versioned_docs`
+   - Creates a physical copy of the versioned platform sidebar in `/docusaurus/platform_versioned_sidebars`
 
 3. Test your build locally to make sure everything looks as expected. Verify:
-
    - The docs site builds locally
    - Your local Docusaurus build doesn't report new broken links
    - The version selector in the navigation contains your new version

docs/platform/readme.md

@@ -27,10 +27,12 @@ Airbyte is available as a self-managed, hybrid, or fully managed cloud solution.
 
 ### Cloud and hybrid plans
 
-<Grid columns="3">
+<Grid columns="2">
 
 <CardWithIcon title="Standard" description="A cloud solution that provides a fully managed experience for data replication. Focus on moving data while Airbyte manages the infrastructure. Free 30-day trial." ctaText="Sign up" ctaLink="https://cloud.airbyte.com/signup" icon="fa-cloud" />
 
+<CardWithIcon title="Plus" description="A cloud solution with all the capabilities of Standard, plus higher priority support and predictable, capacity-based annual pricing." ctaText="Talk to Sales" ctaLink="https://airbyte.com/company/talk-to-sales" icon="fa-lock" />
+
 <CardWithIcon title="Pro" description="A cloud solution for organizations looking to scale efficiently. Role based access control, single sign on, and more ensure Pro is a robust solution that can grow with your team." ctaText="Talk to Sales" ctaLink="https://airbyte.com/company/talk-to-sales" icon="fa-lock" />
 
 <CardWithIcon title="Enterprise Flex" description="An enterprise-grade, hybrid solution with for organizatons seeking the convenience of a fully managed solution with separate data planes for compliance and data sovereignty." ctaText="Learn more" ctaLink="enterprise-flex" icon="fa-lock" />
@@ -43,7 +45,7 @@ Once your Airbyte instance is up and running, there's a way to use Airbyte that'
 
 ### User interface
 
-Self-managed and cloud plans come with a carefully-crafted user interface that walks you through setting up connections and automating syncs. This is a great choice if you're not a developer, aren't concerned about version control, or you're just seeing what Airbyte can do for you.
+Self-managed and cloud plans come with a carefully crafted user interface that walks you through setting up connections and automating syncs. This is a great choice if you're not a developer, aren't concerned about version control, or you're just seeing what Airbyte can do for you.
 
 ### API and Python SDK {#api-sdk}
 

docusaurus/src/components/HeaderDecoration.jsx

@@ -261,14 +261,30 @@ const ConnectorMetadataCallout = ({
           <Chip className={isCloud ? styles.available : styles.unavailable}>
             <EnabledIcon isEnabled={isCloud} /> Standard
           </Chip>
-          <Chip className={isEnterprise || isCloud ? styles.available : styles.unavailable}>
+          <Chip className={isCloud ? styles.available : styles.unavailable}>
+            <EnabledIcon isEnabled={isCloud} /> Plus
+          </Chip>
+          <Chip
+            className={
+              isEnterprise || isCloud ? styles.available : styles.unavailable
+            }
+          >
             <EnabledIcon isEnabled={isEnterprise || isCloud} /> Pro
           </Chip>
-          <Chip className={isEnterprise || isCloud ? styles.available : styles.unavailable}>
+          <Chip
+            className={
+              isEnterprise || isCloud ? styles.available : styles.unavailable
+            }
+          >
             <EnabledIcon isEnabled={isEnterprise || isCloud} /> Enterprise Flex
           </Chip>
-          <Chip className={isEnterprise || isOss ? styles.available : styles.unavailable}>
-            <EnabledIcon isEnabled={isEnterprise || isOss} /> Self-Managed Enterprise
+          <Chip
+            className={
+              isEnterprise || isOss ? styles.available : styles.unavailable
+            }
+          >
+            <EnabledIcon isEnabled={isEnterprise || isOss} /> Self-Managed
+            Enterprise
           </Chip>
           <Chip className={isOss ? styles.available : styles.unavailable}>
             <EnabledIcon isEnabled={isOss} /> PyAirbyte
@@ -334,7 +350,12 @@ const ConnectorMetadataCallout = ({
   </Callout>
 );
 
-const ConnectorTitle = ({ iconUrl, originalTitle, isArchived, enterpriseConnector }) => (
+const ConnectorTitle = ({
+  iconUrl,
+  originalTitle,
+  isArchived,
+  enterpriseConnector,
+}) => (
   <div className={styles.header}>
     <img src={iconUrl} alt="" className={styles.connectorIcon} />
     <h1 data-enterprise-connector={enterpriseConnector}>
@@ -375,9 +396,7 @@ export const HeaderDecoration = ({
 
   return (
     <>
-      <div
-        className={styles.connectorHeader}
-      >
+      <div className={styles.connectorHeader}>
         <ConnectorTitle
           iconUrl={iconUrl}
           originalTitle={originalTitle}

docusaurus/src/components/ProductInformation.jsx

@@ -44,10 +44,22 @@ export const ProductInformation = ({ products }) => {
 
   return (
     <div className={styles.badges}>
-      <Badge available={ossCommunity} title="Formerly Self-Managed Community">Core</Badge>
-      <Badge available={cloud && !cloudTeams && !enterpriseFlex} title="Formerly Cloud">Standard</Badge>
-      <Badge available={cloud || cloudTeams} title="Formerly Cloud Teams">Pro</Badge>
-      <Badge available={cloud || cloudTeams || enterpriseFlex}>Enterprise Flex</Badge>
+      <Badge available={ossCommunity} title="Formerly Self-Managed Community">
+        Core
+      </Badge>
+      <Badge
+        available={cloud && !cloudTeams && !enterpriseFlex}
+        title="Formerly Cloud"
+      >
+        Standard
+      </Badge>
+      <Badge available={cloud && !cloudTeams && !enterpriseFlex}>Plus</Badge>
+      <Badge available={cloud || cloudTeams} title="Formerly Cloud Teams">
+        Pro
+      </Badge>
+      <Badge available={cloud || cloudTeams || enterpriseFlex}>
+        Enterprise Flex
+      </Badge>
       <Badge available={ossEnterprise}>Self-Managed Enterprise</Badge>
       {embedded && <Badge available={true}>Embedded</Badge>}
       <a