Merge branch 'develop' into MStephen024-patch-2

Author: cmastr

CODEOWNERS

@@ -41,10 +41,10 @@ CODEOWNERS  @segmentio/segment-doc-team
 
 
 # Engage
-/src/engage/ @pwseg @rchinn-segment
+/src/engage/ @pwseg 
 
 # Unify
-/src/unify @rchinn-segment
+/src/unify @pwseg 
 
 # Protocols owners
 /src/protocols @forstisabella

CONTRIBUTING.md

@@ -77,6 +77,16 @@ Sources pages check if the source is a cloud-app, then include information about
 
 Content with in each `.md` file is markdown. For information about styling, and available extensions, see `_src/utils/formatguide.md` or the live version [here](https://segment.com/docs/utils/formatguide).
 
+## Building a preview
+
+Netlify allows you to build a preview environment on any PR you create in GitHub. This is helpful when you want to send out a review, and the formatting and design are important to those reviewers. 
+
+To build a preview site, add `[netlify-build]` to a commit message on your PR. Here's an example of what the preview build will look like: 
+
+https://github.com/segmentio/segment-docs/pull/6051#issuecomment-1942723573 
+
+You can rebuild the preview by adding a new commit with  `[netlify-build]` in the commit message. 
+
 ### Front matter
 
 Repository Markdown files often contain front matter metadata, which you'll find at the top of the file. These front matter variables instruct Jekyll how to build and render the page as HTML.
@@ -112,3 +122,4 @@ Front matter variables have unique functions, including the following:
 - `redirect_from`: Defaults to null. Takes an array of URLs from the front matter in a file, and generates a "stub" page at each URL at build-time. Each stub file redirects to the original file. Use the path from the root of the content directory, for example `/connections/destinations/catalog/` rather than `/docs/connections/destinations/catalog/`. **Note** We are mostly using NGINX redirects for SEO purposes. Approximately quarterly, we'll collect these and add them to NGINX.
 - `seo-changefreq`: default: `weekly `. Use the values [in the sitemap spec](https://www.sitemaps.org/protocol.html#xmlTagDefinitions). - sets the `changefreq` tag in the sitemap.xml generator, which tells search crawlers how often to check back.
 - `seo-priority`: values from `1.0` to `0.1`, default: `0.5 `. Sets the `Priority` tag in the sitemap
+- `engage`: defaults to false. Hides the connection modes table and adds a note in the Destination Info box that reads "This destination is **only** compatible with [Twilio Engage](https://segment.com/docs/engage/)."

README.md

@@ -11,11 +11,25 @@ This repository contains the documentation website code and source files for htt
 
 In this article, find information about:
 
+- Prerequisites
 - Contributing
 - A list of READMEs
 - Code of conduct
 - License agreement
 
+## Prerequisites 
+The following are a list of prerequisites you may want to consider downloading and installing to successfully contribute to the Segment docs repo:
+
+1. Download and install a source code editor like [Visual Studio Code](https://code.visualstudio.com/download). 
+1. Download and install a package manager such as [Homebrew](https://brew.sh/) to install new software.
+1. [Create an account on GitHub](https://docs.github.com/en/get-started/quickstart/creating-an-account-on-github) if you don't have one already, or sign in with your existing GitHub account.
+1. Add the GitHub extension to your editor (in VSC: https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github).
+1. [Clone](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) the Segment docs repo.
+1. Download and install the latest version of [node.js](https://nodejs.org/en/download). Consider using a version manager such as [ASDF](https://github.com/asdf-vm/asdf) or [nvm-windows](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows).
+1. Install dependencies 
+  `npm i`
+1. Install [vale](https://docs.errata.ai/vale/install). An [ASDF plugin](https://github.com/osg/asdf-vale) is also available.
+
 ## Contributing
 
 The Segment docs team accepts contributions in the form of issues and pull requests.

ignore-links.txt

@@ -71,3 +71,10 @@ https://segment.com/docs/connections/sources/catalog/cloud-apps/snowflake/
 https://segment.com/docs/connections/destinations/catalog/adobe-target-cloud-mode/
 https://segment.com/docs/connections/destinations/catalog/adobe-target-web/
 https://segment.com/docs/connections/destinations/catalog/google-ads-remarketing-lists/
+https://compose.aampe.com/configure/integrations
+https://everboarding.trybento.co/data
+https://app.getcorrelated.com/integrations
+https://app.launchdarkly.com/default/production/debugger/goals
+https://www.app.metricstory.ai/account/apikeys
+https://app.unstack.com/login
+https://github.com/fubotv/segment-analytics-android/pull/1

scripts/catalog/updateDestinations.js

@@ -102,10 +102,11 @@ const updateDestinations = async () => {
         return clonedObj;
       };
 
-      // I honestly don't remember why I did this.
-      // I think someone wanted to mention support for the Screen method to whatever destination that is
+      // The screen method is not returned as a method from the public API, so if a destination wants to 
+      // show screen as a supported method in `destination-dossier.html` then add the destination id here
+      const destinationsThatSupportScreen = ['63e42b47479274407b671071', '65ccc6147108efc0cf5c6fe1']
       destination.supportedMethods.screen = false;
-      if (destination.id == '63e42b47479274407b671071') {
+      if (destinationsThatSupportScreen.includes(destination.id)) {
         destination.supportedMethods.screen = true;
       }
 
@@ -141,7 +142,8 @@ const updateDestinations = async () => {
         connection_modes,
         settings,
         actions,
-        presets
+        presets,
+        partnerOwned: destination.partnerOwned
       };
 
       // Add the updated destination to the destinationsUpdated array

scripts/catalog/utilities.js

@@ -172,4 +172,4 @@ exports.getCatalog = getCatalog;
 exports.getConnectionModes = getConnectionModes;
 exports.isCatalogItemHidden = isCatalogItemHidden;
 exports.sanitize = sanitize;
-exports.doesCatalogItemExist = doesCatalogItemExist;
+exports.doesCatalogItemExist = doesCatalogItemExist;

src/_data/actions/braze-cloud.yml

@@ -173,7 +173,7 @@ actions:
       description: Set to true to use the Braze API in "Update Only" mode.
       default: false
   - action: Track Purchase
-    blurb: Track Purchase sends Braze a Track Purchase call when the destination recieves any event that matches the specified name.
+    blurb: Track Purchase sends Braze a Track Purchase call when the destination receives any event that matches the specified name.
     fields:
     - name: Time
       description: The timestamp of when the event occured.

src/_data/actions/braze-web.yml

@@ -221,7 +221,7 @@ actions:
       description: Set to true to use the Braze API in "Update Only" mode.
       default: false
   - action: Track Purchase
-    blurb: Track Purchase sends Braze a Track Purchase call when the destination recieves any event named `Order Completed`.
+    blurb: Track Purchase sends Braze a Track Purchase call when the destination receives any event named `Order Completed`.
     fields:
     - name: Time
       description: The timestamp of when the event occured.

src/_data/catalog/beta_sources.yml

@@ -0,0 +1,26 @@
+# This file is manually generated. 
+# Add the ids of beta sources to give them a beta flag on the catalog page.
+# (/docs/connections/sources/catalog)
+
+- 8aF29Uq46F
+- QhEUZnE5uF
+- Zd5BXedXsa
+- glwy6LwOVo
+- 3x07B5Dn5h
+- DY0B0Q2Gce
+- n8YgCndi75
+- 9TYqEh3nMe
+- xqegKCQA0W
+- L9XPA9n2Mc
+- kpDbTUR9oD
+- wFC7PGNwGR
+- vMEJCURfHh
+- EjYD7n6dOa
+- VETiUX9u66
+- NC2jsEkA8Y
+- o9OyD6xsVJ
+- ODf0vA6dcH
+- YWOGVbyMVz
+- CwGEZ7eCcA
+- xeZMgSrtAQ
+- VShGHAfvlr

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-09-28 
+# destination categories last updated 2024-05-30 
 items:
 - display_name: A/B Testing
   slug: a-b-testing