Remove BDP wording (#1436)

* Update offering banner

* Replace some BDP mentions

* Start updating offerings pages

* Update page describing different offerings

* Tidy up the rest of Get started

* Edit the Snowplow CLI reference

* Update a path

* Remove some more BDPs

* Clarify self-hosted offerings

* Fix doubled words

* Remove BDPs outside of docs folder

* Replace in marketing plugin metadata

* Rework the offerings page again

* Tidy up Glossary links

* Fix links

* Make changes following review

* Completely remove the BDP/CE admons

* remove BDP from event forwarding diagram

* Restore Azure app name

* Restore Azure bits I missed the first time

---------

Co-authored-by: Phil Catterall <[email protected]>

Author: mscwilson

.github/styles/Snowplow/Acronyms.yml

@@ -65,7 +65,7 @@ exceptions:
   - ZIP
 
   # Added for Snowplow
-  - BDP
+  - CDI
   - DNS
   - SQS
   - UUID

.github/styles/config/vocabularies/snowplow/accept.txt

@@ -53,7 +53,7 @@ Data Product Studio
 Data Model Packs
 Data Model Pack
 AWS Console
-BDP Console
+Snowplow Console
 Iglu Central
 Iglu Server
 Igluctl

CLAUDE.md

@@ -48,7 +48,7 @@
 * Mix prose and lists appropriately: use prose to explain concepts, lists for configuration options or step-by-step items
 
 ### Snowplow terminology
-* **Capitalized**: Data Product Studio, Snowtype, Snowplow BDP, Signals
+* **Capitalized**: Data Product Studio, Snowtype, Snowplow CDI, Signals
 * **Context-capitalized**: Collector, Enrich, specific Loaders
 * **Not capitalized**: entities, events, schemas, data structures
 * Use "entity" not "context", "self-describing event" not "unstructured event"
@@ -120,11 +120,6 @@ Important cautions about data loss, security, or breaking changes
 * **Tip**: performance improvements, recommended workflows, pro tips
 * **Warning**: data loss risks, security considerations
 
-### BDP vs self-hosted
-* Mark BDP-only features in frontmatter: `sidebar_custom_props: offerings: - bdp`
-* Note when BDP provides built-in functionality, mention self-hosted alternatives
-* **Do not mention "Community Edition"** - use "self-hosted" instead but otherwise prefer not to mention
-
 ### Images
 * Formats: `.webp` (preferred), `.png`, `.jpg`
 * Descriptive filenames and alt text

README.md

@@ -10,7 +10,6 @@ This is the source for https://docs.snowplow.io/docs.
 - [Organizing content](#organizing-content)
   - [Sidebar](#sidebar)
     - [Updating sidebar attributes for multiple sections at once](#updating-sidebar-attributes-for-multiple-sections-at-once)
-  - [Offerings](#offerings)
   - [Links](#links)
   - [Concepts](#concepts)
   - [Reusable fragments](#reusable-fragments)
@@ -143,26 +142,6 @@ It'll update the `index.md` files as appropriate.
 
 You can now delete the `update_attributes_here.txt` file.
 
-### Offerings
-
-Some documentation is only relevant to a particular offering. You can indicate it like this:
-```
----
-title: ...
-...
-sidebar_custom_props:
-  offerings:
-    - bdp
-...
----
-```
-
-This will result in an icon appearing in the sidebar, as well as an automatic banner on the page, specifying that the docs only apply to a given offering.
-
-The available values are: `bdp` and `community`. Do not specify both values at once — if a piece of documentation is relevant to all offerings, there should be no `offerings` property as that’s the default.
-
-Whenever the same functionality can be achieved in multiple offerings but in a different way (e.g. managing schemas), create a parent folder (“Managing schemas”) that’s offering-neutral, and then add offering-specific pages inside it. This way, other pages can link to the generic page without having to specify different methods for different offerings.
-
 ### Links
 
 For links within this documentation, please end the link with `/index.md`. This way all links will be checked, and you’ll get an error if a link is broken at any point.

docs/account-management/index.md

@@ -4,23 +4,21 @@ date: "2020-02-15"
 sidebar_position: 9
 sidebar_custom_props:
   header: " "
-  offerings:
-    - bdp
 sidebar_label: "Account management"
 ---
 
-Manage your account configuration and users using the Snowplow BDP Console. You can also use the underlying API directly. This page describes how to acquire an API key.
+Manage your account configuration and users using the Snowplow Console. You can also use the underlying API directly. This page describes how to acquire an API key.
 
 ## Credentials API
 
-The API that drives BDP Console's functionality is [publicly documented](https://console.snowplowanalytics.com/api/msc/v1/docs/index.html?url=/api/msc/v1/docs/docs.yaml) and available for our customers to invoke via code. All calls to it need to be properly authenticated using JSON Web Tokens (JWT) that can be acquired via the Credentials API.
+The API that drives Console's functionality is [publicly documented](https://console.snowplowanalytics.com/api/msc/v1/docs/index.html?url=/api/msc/v1/docs/docs.yaml) and available for our customers to invoke via code. All calls to it need to be properly authenticated using JSON Web Tokens (JWT) that can be acquired via the Credentials API.
 
 The process for creating a key has been improved over time. We recommend using the v3 process.
 
 
 ### Version 3
 
-The following view is available to all customers under [BDP Console settings](https://console.snowplowanalytics.com/credentials):
+The following view is available to all customers under [Console settings](https://console.snowplowanalytics.com/credentials):
 
 ![](images/accessing-generated-api-keys.png)
 
@@ -95,10 +93,10 @@ Authenticating with v2 only required the API key secret. While this method and t
 
 ### Version 1
 
-Previously, BDP Console was using the Password authentication flow to support machine-to-machine (m2m) applications. Under that scenario a BDP customer had to create a bot user in their account, retrieve a client ID and a client secret, and use all three to acquire a JWT. Customers who have enabled these credentials in the past will see the following panel in their Console account settings:
+Previously, Console was using the Password authentication flow to support machine-to-machine (m2m) applications. Under that scenario a customer had to create a bot user in their account, retrieve a client ID and a client secret, and use all three to acquire a JWT. Customers who have enabled these credentials in the past will see the following panel in their Console account settings:
 
 ![](images/image-2.png)
 
-Legacy Snowplow BDP credentials management
+Legacy Snowplow credentials management
 
 This method and the respective credentials still work for those who have been using them, however we strongly advise that customers upgrade to the current iteration where the only secret to be used by m2m applications is an API key which can be exchanged for a JWT.

docs/account-management/managing-permissions/index.md

@@ -8,7 +8,7 @@ To set a users permissions, navigate to `Manage users` and then to the user whos
 
 ## What permissions can be set?
 
-Snowplow BDP Console sets permissions for each area of Console as summarized below:
+Snowplow Console sets permissions for each area of Console as summarized below:
 
 | **Console feature** | **Description**                                                                                                               | **Possible permissions**                                                     |
 | ------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |

docs/api-reference/enrichment-components/configuration-reference/index.md

@@ -32,8 +32,8 @@ To accept the terms of license and run Enrich, set the `ACCEPT_LIMITED_USE_LICEN
 | `monitoring.metrics.statsd.prefix` | Optional. Default: `snowplow.enrich`. Pefix of StatsD metric names. |
 | `monitoring.healthProbe.port` (since *6.0.0*) | Optional. Default: `8000`. Open a HTTP server that returns OK only if the app is healthy. |
 | `monitoring.healthProbe.unhealthyLatency` (since *6.0.0*) | Optional. Default: `2 minutes`. Health probe becomes unhealthy if any received event is still not fully processed before this cutoff time. |
-| `telemetry.disable` | Optional. Set to `true` to disable [telemetry](/docs/get-started/snowplow-community-edition/telemetry/index.md). |
-| `telemetry.userProvidedId` | Optional. See [here](/docs/get-started/snowplow-community-edition/telemetry/index.md#how-can-i-help) for more information. |
+| `telemetry.disable` | Optional. Set to `true` to disable [telemetry](/docs/get-started/self-hosted/telemetry/index.md). |
+| `telemetry.userProvidedId` | Optional. See [here](/docs/get-started/self-hosted/telemetry/index.md#how-can-i-help) for more information. |
 | `validation.acceptInvalid` (since *6.0.0*) | Optional. Default: `false`. Enrich *3.0.0* introduces the validation of the enriched events against atomic schema before emitting. If set to `false`, a failed event will be emitted instead of the enriched event if validation fails. If set to `true`, invalid enriched events will be emitted, as before. |
 | `validation.atomicFieldsLimits` (since *4.0.0*) | Optional. For the defaults, see [here](https://github.com/snowplow/enrich/blob/master/modules/common/src/main/resources/reference.conf). Configuration for custom maximum atomic fields (strings) length. It's a map-like structure with keys being atomic field names and values being their max allowed length. |
 | `validation.maxJsonDepth` (since *6.0.0*) | Optional. Default: `40`. Maximum allowed depth for the JSON entities in the events. Event will be sent to bad row stream if it contains JSON entity with a depth that exceeds this value. |

docs/api-reference/failed-events/index.md

@@ -32,7 +32,7 @@ In order for an event to be processed successfully:
 
 If your pipeline is generating schema violations, it might mean there is a problem with your tracking, or a problem with your [Iglu resolver](/docs/api-reference/iglu/iglu-resolver/index.md) which lists where schemas should be found. The error details in the schema violation JSON object should give you a hint about what the problem might be.
 
-Snowplow BDP customers should check in the Snowplow BDP Console that all data structures are correct and have been [promoted to production](/docs/data-product-studio/data-structures/manage/index.md). Snowplow Community Edition users should check that the Enrichment app is configured with an [Iglu resolver file](/docs/api-reference/iglu/iglu-resolver/index.md) that points to a repository containing the schemas.
+Snowplow customers should check in the Snowplow Console that all data structures are correct and have been [promoted to production](/docs/data-product-studio/data-structures/manage/index.md). Snowplow Self-Hosted users should check that the Enrichment app is configured with an [Iglu resolver file](/docs/api-reference/iglu/iglu-resolver/index.md) that points to a repository containing the schemas.
 
 Next, check the tracking code in your custom application, and make sure the entities you are sending conform to the schema definition.
 

docs/api-reference/index.md

@@ -7,4 +7,4 @@ sidebar_label: "Reference"
 
 This section contains detailed technical information about Snowplow components.
 
-Some of the information is relevant only for [Community Edition](/docs/get-started/snowplow-community-edition/index.md) users, as [Snowplow BDP](/docs/get-started/snowplow-bdp/index.md) customers won't need to configure all their own components.
+Some of the information is relevant only for [Snowplow Self-Hosted](/docs/get-started/index.md#self-hosted) users, as [Snowplow CDI](/docs/get-started/index.md#customer-data-infrastructure) customers won't need to configure all their own components.

docs/api-reference/loaders-storage-targets/databricks-streaming-loader/configuration-reference/_common_config.md

@@ -94,11 +94,11 @@ import Link from '@docusaurus/Link';
 </tr>
 <tr>
     <td><code>telemetry.disable</code></td>
-    <td>Optional. Set to <code>true</code> to disable <Link to="/docs/get-started/snowplow-community-edition/telemetry/">telemetry</Link>.</td>
+    <td>Optional. Set to <code>true</code> to disable <Link to="/docs/get-started/self-hosted/telemetry/">telemetry</Link>.</td>
 </tr>
 <tr>
     <td><code>telemetry.userProvidedId</code></td>
-    <td>Optional. See <Link to="/docs/get-started/snowplow-community-edition/telemetry/#how-can-i-help">here</Link> for more information.</td>
+    <td>Optional. See <Link to="/docs/get-started/self-hosted/telemetry/#how-can-i-help">here</Link> for more information.</td>
 </tr>
 <tr>
     <td><code>http.client.maxConnectionsPerServer</code></td>