[netlify-ignore]Merge branch 'master' into ajs2_devx

Author: markzegarelli

src/_data/sidenav/main.yml

@@ -263,21 +263,21 @@ sections:
         title: Overview
       - path: /personas/audiences/account-audiences
         title: Account-level Audiences
-  - section_title: Journeys
-    slug: /personas/journeys
-    section:
-      - path: /personas/journeys
-        title: Journeys Overview
-      - path: /personas/journeys/build-journey
-        title: Build a Journey
-      - path: /personas/journeys/send-data
-        title: Send Data to Destinations
-      - path: /personas/journeys/faq-best-practices
-        title: Journeys Best Practices and FAQ
-      - path: /personas/journeys/use-cases
-        title: Example Journeys Use Cases
-      - path: /personas/journeys/key-terms
-        title: Journeys Glossary
+  # - section_title: Journeys
+  #   slug: /personas/journeys
+  #   section:
+  #     - path: /personas/journeys
+  #       title: Journeys Overview
+  #     - path: /personas/journeys/build-journey
+  #       title: Build a Journey
+  #     - path: /personas/journeys/send-data
+  #       title: Send Data to Destinations
+  #     - path: /personas/journeys/faq-best-practices
+  #       title: Journeys Best Practices and FAQ
+  #     - path: /personas/journeys/use-cases
+  #       title: Example Journeys Use Cases
+  #     - path: /personas/journeys/key-terms
+  #       title: Journeys Glossary
   - path: /personas/using-personas-data
     title: Using Personas data
   - path: /personas/warehouses

src/_release_notes/2021-05-25-journeys.md renamed to src/_release_notes_drafts/DRAFT-journeys.md

@@ -1,5 +1,6 @@
 ---
 title: Build a Journey
+hidden: true
 ---
 
 Follow along for the steps required to create a new Journey.

src/personas/journeys/build-journey.md

@@ -1,5 +1,6 @@
 ---
 title: Journeys Best Practices and FAQ
+hidden: true
 ---
 ## Best practices
 

src/personas/journeys/faq-best-practices.md

@@ -1,5 +1,6 @@
 ---
 title: Journeys Overview
+hidden: true
 ---
 
 Journeys, a feature of Segment Personas, provides a way for marketers to personalize experiences through planning how and when to engage customers with the right campaigns and messages.

src/personas/journeys/index.md

@@ -1,5 +1,6 @@
 ---
 title: Journeys Key Terms
+hidden: true
 ---
 
 Keep the following terms in mind as you begin to explore Journeys.

src/personas/journeys/key-terms.md

@@ -1,5 +1,6 @@
 ---
 title: Send Journeys data to a Destination
+hidden: true
 ---
 
 When you send data to destinations, you send a series of events or user lists, depending on the destination type.

src/personas/journeys/send-data.md

@@ -1,5 +1,6 @@
 ---
 title: Example Journeys Use Cases
+hidden: true
 ---
 
 To help you get underway, you can reference these sample Journeys.

src/personas/journeys/use-cases.md

@@ -71,7 +71,7 @@ When requests to downstream destinations fail, Segment makes additional attempts
 <tr>
 <td>Identity Merges</td>
 <td>100 merges</td>
-<td>Personas supports up to 100 merges per profile in its identity graph. A merge occurs when two existing profiles are joined together by a common `external_id`. For example, if a user starts their journey on mobile, and then signs in through a web application, those two user profiles are joined together by a common identifier like a `user_id`. Messages that attempt additional merges are usually a sign of a corrupt profile and are dropped.
+<td>Personas supports up to 100 merges per profile in its identity graph. A merge occurs when two existing profiles are joined together by a common `external_id`. For example, if a user starts on mobile, and then signs in through a web application, those two user profiles are joined together by a common identifier like a `user_id`. Messages that attempt additional merges are usually a sign of a corrupt profile and are dropped.
 <br /><br />
 Once the limit is reached, Segment rejects additional events.</td>
 </tr>
@@ -171,7 +171,7 @@ Contact your account team to customize your schedule.</td>
 </table>
 
 
-## Journeys
+<!-- ## Journeys
 
 
 In addition to the [Personas Default Limits](#default-limits), Journeys enforces a set of default limits to ensure the reliability and performance of the feature.
@@ -182,4 +182,4 @@ In addition to the [Personas Default Limits](#default-limits), Journeys enforces
 | Journey steps | 20 steps per Journey             | This applies to certain steps:<br><br>- Initial cohort: 1<br>- Wait for condition: 1<br>- True / False Split: 1<br>- Multi-Branch Split: Number of branches<br>- Send to Destinations: 1<br><br>Once the limit is reached, you will be unable to add additional steps to the Journey. |
 | Journey Name  | Maximum length of 73 characters  | Once the limit is reached, you cannot add additional characters to the name.                                                                                                                                                                                               |
 | Step Name     | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name.                                                                                                                                                                                               |
-| Key           | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key.                                                                                                                                                                                                |
+| Key           | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key.                                                                                                                                                                                                | -->