merge to staging. I need to figure out how to do this from the command line.

_config.yml

@@ -13,6 +13,8 @@ defaults:
       layout: "page"
       hidden: false
       beta: false
+      seo-priority: 0.5
+      seo-changefreq: weekly
   - scope:
       path: "connections/destinations"
     values:

_data/sidenav/default.yml

@@ -1,48 +1,5 @@
 ---
 sections:
-- section_title: Connections
-  section:
-  - path: "/connections/spec"
-    title: Spec
-  - section_title: Sources
-    slug: connections/Sources
-    section:
-    - path: "/connections/sources"
-      title: Overview
-    - path: "/connections/sources/visual-tagger"
-      title: "Visual tagger"
-    - path: "connections/sources/faq"
-      title: "FAQ"
-    - path: "/connections/sources/catalog"
-      title: Sources catalog
-  - section_title: Destinations
-    slug: connections/destinations
-    section:
-    - path: "/connections/destinations"
-      title: Overview
-    - path: "/connections/destinations/destination-filters"
-      title: Destinations Filters
-    - path: "/connections/destinations/catalog"
-      title: Destinations catalog
-  - section_title: Warehouses
-    slug: connections/warehouses
-    section:
-      - path: "/connections/warehouses"
-        title: Overview
-      - path: "/connections/warehouses/choose-warehouse"
-        title: Choosing a Warehouse
-      - path: "/connections/warehouses/add-warehouse-users"
-        title: Add users to a Warehouse
-      - path: "/connections/warehouses/redshift-faq"
-        title: "Redshift Best Practices"
-      - path: "/connections/warehouses/redshift-tuning"
-        title: "Improving Redshift performance"
-      - path: "/connections/warehouses/warehouse-errors"
-        title: "Warehouse Error codes"
-      - path: "/connections/warehouses/faq"
-        title: Warehouses FAQs
-      - path: "/connections/warehouses/catalog"
-        title: Warehouses Catalog
 - section_title: Guides
   section:
   - path: "/guides"
@@ -174,6 +131,37 @@ sections:
       title: How do I find out my usage data?
     - path: "/guides/usage-and-billing/volume-and-pricing"
       title: How does my event and object volume impact my pricing?
+- section_title: Connections
+  section:
+  - path: "/connections/spec"
+    title: Spec
+  - section_title: Sources
+    slug: connections/Sources
+    section:
+    - path: "/connections/sources"
+      title: Overview
+    - path: "/connections/sources/visual-tagger"
+      title: "Visual tagger"
+    - path: "/connections/sources/faq"
+      title: "FAQ"
+    - path: "/connections/sources/catalog"
+      title: Sources catalog
+  - section_title: Destinations
+    slug: connections/destinations
+    section:
+    - path: "/connections/destinations"
+      title: Overview
+    - path: "/connections/destinations/destination-filters"
+      title: Destinations Filters
+    - path: "/connections/destinations/catalog"
+      title: Destinations catalog
+  - section_title: Warehouses
+    slug: connections/warehouses
+    section:
+      - path: "/connections/warehouses"
+        title: Overview
+      - path: "/connections/warehouses/catalog"
+        title: Warehouses catalog
 - section_title: Personas
   section:
   - path: "/personas"

_includes/content/spec-field-page-name.md

@@ -2,6 +2,6 @@
   <td>`name` *optional*</td>
   <td>String</td>
   <td>Name of the page
-    <p> For example, most sites have a “Signup” page that can be useful to tag, so you can see users as they move through your funnel.</p>
+    <p> For example, most sites have a "Signup" page that can be useful to tag, so you can see users as they move through your funnel.</p>
   </td>
 </tr>

_includes/content/whats-a-destination.md

@@ -0,0 +1,9 @@
+Destinations are business tools or apps that you can connect to the data flowing through Segment. Some of our most popular destinations are Google Analytics, Mixpanel, KISSmetrics, Customer.io, Intercom, and KeenIO.
+
+All of these tools run on the same data: who are your customers and what are they doing? But each tool requires that you send that data in a slightly different format, which means that you'd have to write code to track all of this information, again and again, for each tool, on each page of your app or website.
+
+Enter Segment. Do it once!
+
+We eliminate this process by introducing an abstraction layer. You send your data to us, and we understand how to translate it so we can send it along to any destination. You enable destinations from the catalog in the Segment App, and user data immediately starts flowing into those tools. No extra code required!
+
+We support many categories of destinations, from advertising to marketing, email to customer support, CRM to user testing, and even data warehouses. You can view a complete list of our [destinations](/docsv2/connections/destinations/catalog/) or check out our [destination page](https://segment.com/destinations) for a searchable list broken down by category.

_includes/content/whats-a-source.md

@@ -0,0 +1,10 @@
+In Segment, you create a source (or more than one!) for each website or app you want to track. While it's not required that you have a single Source for each server, site or app, we **highly recommend** creating a Source for each unique source of data.
+
+Sources belong to a workspace, and the URL for a source look something like this:
+`https://segment.com/<my-workspace>/sources/<my-source-name>/`
+
+You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment JavaScript library](https://segment.com/docs/sources/website/analytics.js/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/sources/website/analytics.js/quickstart/) includes:
+
+```js
+analytics.load("YOUR_WRITE_KEY");
+```

_includes/content/whats-a-warehouse.md

@@ -0,0 +1,13 @@
+A warehouse is a central repository of data collected from one or more sources. This is what commonly comes to mind you think about a relational database: structured data that fits neatly into rows and columns.
+
+In Segment, a Warehouse is a special type destination. Instead of streaming data to the destination all the time, we load data to them in bulk at a regular intervals. When we load data, we insert and update events and objects, and automatically adjust their schema to fit the data you’ve sent to Segment.
+
+When selecting and building a data warehouse, there are three questions to consider:
+
+1.  What type of data will be collected?
+2.  How many data sources will there be?
+3.  How will the data be used?
+
+Relational databases are great when you know and predefine the information collected and how it will be linked. This is usually the type of database used in the world of user analytics. For instance, a users table might be populated with the columns "name", "email address", "plan name", etc.
+
+Examples of data warehouses include Amazon Redshift, Google BigQuery, MySQL, and Postgres.

_includes/content/whats-a-workspace.md

@@ -0,0 +1,3 @@
+A workspace is a group of sources that can be administered and billed together. Workspaces let you collaborate with team members, add permissions, and share sources across your whole team using a shared billing account.
+
+Workspaces help companies manage access for multiple users and data sources. When you are logged in to your Segment account, you can create a new workspace from the menu.

_templates/destinations.example.yml

@@ -11873,7 +11873,7 @@ destinations:
     required: false
     string_validators:
       regexp: ''
-    description: To find your API key, log into Pendo and navigate to “your user name”
+    description: To find your API key, log into Pendo and navigate to "your user name"
       > Site settings > Basic Information > API key. If your account has not fully
       been set up yet, you can see the API key inside of the code snippet on the Pendo
       setup page.
@@ -14653,11 +14653,11 @@ destinations:
     required: true
     string_validators:
       regexp: "^.{8,}$"
-    description: To find your key, log into Split and navigate to “Admin Settings”
-      > “Integrations” > select your desired workspace > “Segment”. There you can
+    description: To find your key, log into Split and navigate to "Admin Settings"
+      > "Integrations" > select your desired workspace > "Segment". There you can
       find the key for each configured integration. If you don’t have an integration
-      configured, be sure to configure your integration in the section “Configure
-      as a destination in Segment” and click save to generate a key. For more information,
+      configured, be sure to configure your integration in the section "Configure
+      as a destination in Segment" and click save to generate a key. For more information,
       learn more in Split’s [integration documentation](https://segment.com/docs/destinations/split/).
     settings: []
 - name: catalog/destinations/stitch-data
@@ -15562,7 +15562,7 @@ destinations:
     required: true
     string_validators:
       regexp: "^[a-zA-Z0-9]*$"
-    description: Drop in the “Integration Key” into your Segment Settings UI which
+    description: Drop in the "Integration Key" into your Segment Settings UI which
       you can find on https://businessapp.b2b.trustpilot.com/#/ecommerce/segment
     settings: []
 - name: catalog/destinations/tune

connections/destinations/catalog/aboardly/index.md

@@ -18,3 +18,6 @@ When you `identify` a user, we'll pass that user's information to Aboardly with
 ## Track
 
 When you `track` an event, we will send that event to Aboardly as a custom event.
+
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/activecampaign/index.md

@@ -13,8 +13,8 @@ This document was last updated on March 27, 2018. If you notice any gaps, outdat
 
 {% include content/connection-modes.md %}
 
-1.  From your Segment UI’s Destinations page click on “Add Destination”.
-2.  Search for “Active Campaign” within the Destinations Catalog and confirm the Source you’d like to connect to.
+1.  From your Segment UI’s Destinations page click on "Add Destination".
+2.  Search for "Active Campaign" within the Destinations Catalog and confirm the Source you’d like to connect to.
 3.  Add your API URL and API Key which can be found in your ActiveCampaign UI Settings page under the Developer tab.
 4.  Since the Segment ActiveCampaign destination integration is 100% handled through Segment, you don't need to install ActiveCampaign site tracking or event tracking Javascript code.
 

connections/destinations/catalog/adobe-analytics/index.md

@@ -451,7 +451,7 @@ You can either send the property value as a string (ie. `'brady'`) or as an arra
 
 ### Merchandising Events
 
-The Merchandising Events settings allow you to set eVars and events on a per-product basis within the “products” string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html).
+The Merchandising Events settings allow you to set eVars and events on a per-product basis within the "products" string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html).
 
 The setting operates as follows:
 

connections/destinations/catalog/adobe-target/index.md

@@ -121,7 +121,7 @@ document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, function() {
 ### Preventing Page Flicker
 
 Page flicker may occur when default content momentarily displays to a visitor
-prior to the A/B “activity” content replacing it. One approach to preventing
+prior to the A/B "activity" content replacing it. One approach to preventing
 page flicker in conjunction with Segment would be to create a global mbox. Adobe
 will automatically set the HTML body style opacity to 0, which keeps the page
 content hidden while allowing the browser to still execute page load. After a

connections/destinations/catalog/adroll/index.md

@@ -17,8 +17,8 @@ This document was last updated on January 26, 2018. If you notice any gaps, outd
 
 {% include content/connection-modes.md %}
 
-1. From your Segment UI’s Destinations page click on “Add Destination”.
-2. Search for “Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to.
+1. From your Segment UI’s Destinations page click on "Add Destination".
+2. Search for "Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to.
 3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`.
 
     ![](images/adroll-pixel.png)

connections/destinations/catalog/adtriba/index.md

@@ -56,3 +56,5 @@ analytics.track('Conversion', {
 Track calls will be sent to Adtriba as a `track` event.
 
 Trigger additional events by using [Semantic Events](https://segment.com/docs/spec/semantic/) in order to enrich the Adtriba machine learning process.
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/adwords-remarketing-lists/index.md

@@ -54,3 +54,5 @@ We attempt to match users in your audience with the identifiers that Google supp
 ### What Adwords platforms are supported?
 
 This destination supports Search, Gmail, and Youtube ad campaigns. Adwords does not support Display campaigns through remarketing lists.
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/adwords/index.md

@@ -216,3 +216,6 @@ The following properties are optional, if you'd like to see more, please get in
 </table>
 
 Here's Google documentation for the endpoint we hit [for iOS apps](https://developers.google.com/app-conversion-tracking/ios/conversion-tracking-server#reporting_in-app_conversions_from_an_analytics_server) and [for Android Apps](https://developers.google.com/app-conversion-tracking/android/conversion-tracking-server#in-app_conversions). It can take 24-48 hours for conversions to show up in the conversions dashboard.
+
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/akita/index.md

@@ -50,3 +50,6 @@ When you call `page`, Segment will send that event to Akita as a `Page View`.
 ## Track
 
 When you call `track`, Segment will send that event to Akita as an `Event`.
+
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/alexa/index.md

@@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd
 
 {% include content/connection-modes.md %}
 
-1. From your Segment UI’s Destinations page click on “Add Destination”.
-2. Search for “Alexa” within the Destinations Catalog and confirm the Source you’d like to connect to.
+1. From your Segment UI’s Destinations page click on "Add Destination".
+2. Search for "Alexa" within the Destinations Catalog and confirm the Source you’d like to connect to.
 3. Fill in your "Account ID" which you can find in the Alexa Javascript snippet. It appears as atrk_acct: 'XXXXXXX'.
 4. Fill in your "Domain" which you can find in the Alexa Javascript snippet. It appears as domain: 'example.com'.
 5. In about 5-10 minutes the CDN will be updated and the Alexa Javascript snippet will be initialized onto your page.

connections/destinations/catalog/all-aboard/index.md

@@ -40,3 +40,5 @@ Segment allows you to expose what your users do in your application. This inform
 For instance, using our simple example above perhaps you only want to invite customers who completed the registration process to an onboarding call. The `finished_registration: TRUE` trait allows you to quickly identify these customers.
 
 Traits are also useful in helping you have a more personal dialog with your trial customers. More personal call invitations encourage your most qualified customers to schedule a call with you.
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/amazon-lambda/index.md

@@ -133,7 +133,7 @@ While setting up the new role, add the policy you created in the previous step.
 
 Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home).
 
-Select the “Trust Relationships” tab, then click the “Edit trust relationship” button.
+Select the "Trust Relationships" tab, then click the "Edit trust relationship" button.
 
 ![](images/LambdaTrustRelationship.png)
 
@@ -170,7 +170,7 @@ If you have multiple Source’s using this Role, replace the `sts:ExternalId` se
 
 ## Configure Segment Lambda Destination
 
-Search for “Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings.
+Search for "Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings.
 
 
 ## FAQ

connections/destinations/catalog/amazon-personalize/index.md

@@ -590,7 +590,7 @@ The "Import user-item interaction data" step is displayed next. To complete this
 
 For the "IAM service role", select "Create a new role" from the dropdown. In the next pop-up, we recommend listing your bucket name in the "Specific S3 buckets" option, but you're free to choose the option that best suits your needs.
 
-Next you will need the location of the CSV file you generated in the earlier steps.  This needs to be configured in the “Data Location” field on this screen.
+Next you will need the location of the CSV file you generated in the earlier steps.  This needs to be configured in the "Data Location" field on this screen.
 
 ![](images/PersonalizeImportJob.png)
 
@@ -692,7 +692,7 @@ While setting up the new role, add the policy you created in the previous step.
 
 Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home).
 
-Select the “Trust Relationships” tab, then click the “Edit trust relationship” button.
+Select the "Trust Relationships" tab, then click the "Edit trust relationship" button.
 
 ![](images/LambdaTrustRelationship.png)
 
@@ -868,7 +868,7 @@ Enter a name for your Event Tracker.
 
 You will need to configure a role for Personalize to that allows it to execute the tracker.  This is the same as the execution role you defined earlier for Personalize:
 
-Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess”
+Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess"
 
 ```
     {
@@ -917,7 +917,7 @@ Often this is automatically included as a policy labelled "AmazonPersonalizeFull
     }
 ```
 
-This may be automatically included as policy “AmazonPersonalize-ExecutionPolicy-<some-set-of-numbers>”
+This may be automatically included as policy "AmazonPersonalize-ExecutionPolicy-<some-set-of-numbers>"
 
 ```
     {
@@ -998,7 +998,7 @@ Your lambda is now ready to receive events from Segment.  Next, you will need to
 
 Once your Lambda function is enabled, you can send it events from Segment using the Personalize Destination.
 
-Search for “Amazon Personalize” in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings.
+Search for "Amazon Personalize" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings.
 
 We allow you to send each call type to a different Lambda. If you leave the Lambda field blank for a given call type, we won’t attempt to send any of those calls.
 

connections/destinations/catalog/appcues/index.md

@@ -116,4 +116,6 @@ lifecycle events that can be tracked:
 * `coachmarks_completed`
 
 To enable this feature, go to the Integrations Settings in Appcues and
-click “Activate” under the Segment integration.
+click "Activate" under the Segment integration.
+
+{% include content/integration-foot.md %}

connections/destinations/catalog/appsflyer/index.md

@@ -11,8 +11,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat
 
 {% include content/connection-modes.md %}
 
-  1. From your Segment UI’s Destinations page click on “Add Destination”.
-  2. Search for “AppsFlyer“ within the Destinations Catalog and confirm the Source you’d like to connect to.
+  1. From your Segment UI’s Destinations page click on "Add Destination".
+  2. Search for "AppsFlyer" within the Destinations Catalog and confirm the Source you’d like to connect to.
   3. Drop in your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account.
   4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration).
   5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically.