Merge pull request #4467 from segmentio/DOC-648

Reverse ETL GA

Author: stayseesong

src/_data/sidenav/main.yml

@@ -142,10 +142,10 @@ sections:
     - path: /connections/sources/catalog
       title: Sources Catalog
       menu_icon: read-more
-    - path: /connections/sources/debugger
-      title: Using the Source Debugger
     - path: /connections/sources/about-cloud-sources
       title: Cloud Sources
+    - path: /connections/sources/debugger
+      title: Source Debugger
     - path: /connections/sources/custom-domains
       title: Set Up a Custom Domain Proxy in Segment
     - path: /connections/sources/visual-tagger
@@ -164,6 +164,20 @@ sections:
       menu_icon: read-more
     - path: /connections/destinations/destination-filters
       title: Destination Filters
+  - section_title: Reverse ETL
+    slug: connections/reverse-etl
+    section:
+    - path: /connections/reverse-etl
+      title: Reverse ETL Overview
+    - section_title: Reverse ETL Source Setup Guides  
+      slug: connections/reverse-etl/reverse-etl-source-setup-guides
+      section: 
+      - path: /connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup
+        title: BigQuery Reverse ETL Setup
+      - path: /connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup
+        title: Redshift Reverse ETL Setup
+      - path: /connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup
+        title: Snowflake Reverse ETL Setup
   - section_title: Functions
     slug: connections/functions
     section:

src/_redirects

@@ -1,4 +1,11 @@
 # Redirects file for Netlify
 
 # Redirect for Profiles -> Unify rename
-/docs/profiles/*                        /docs/unify/:splat
+# /docs/profiles/*                          /docs/unify/:splat
+
+
+# RETL Beta -> GA redirect
+/docs/reverse-etl/                         /docs/connections/reverse-etl
+/docs/reverse-etl/bigquery-setup/          /docs/connections/reverse-etl/reverse-etl-source-setup-guides/bigquery-setup/
+/docs/reverse-etl/redshift-setup/          /docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup/
+/docs/reverse-etl/snowflake-setup/         /docs/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup/

src/connections/destinations/index.md

@@ -11,6 +11,24 @@ Destinations are the business tools or apps that Segment forwards your data to.
 
 Segment has [Sources](/docs/connections/sources/) and [Destinations](/docs/connections/destinations/). Sources send data _into_ Segment, while Destinations receive data _from_ Segment.
 
+## Destination connection types
+Segment has three destination connection types:
+* [Event streams](#event-streams-destinations)
+* [Storage](#storage-destinations)
+* [Reverse ETL](#reverse-etl-destinations)
+
+### Event streams destinations
+Event streams destinations are all destinations that aren't storage or Reverse ETL destinations. Adding these destinations allow you to act on your data and learn more about your customers in real time. These include [Destination Actions](/docs/connections/destinations/actions/). 
+
+### Storage destinations
+Storage destinations enable you to store your raw Segment data. This enables data analysts and data scientists to work with the raw data to derive deeper and more customized insights to support your organization. Learn more from the [storage overview page](/docs/connections/storage/).
+
+### Reverse ETL destinations
+[Reverse ETL](/docs/connections/reverse-etl) destinations are the business tools or apps you use that Segment syncs the data from your warehouse to. 
+
+If your destination is not listed in the Reverse ETL catalog, use the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/) to send data from your Reverse ETL warehouse to other destinations listed in the [catalog](/docs/connections/destinations/catalog/). The Segment Connections destination enables you to mold data extracted from your warehouse in [Segment Spec](docs/connections/spec/) API calls that are then processed by [Segment’s HTTP Tracking API](/docs/connections/sources/catalog/libraries/server/http-api/). The Segment HTTP Tracking API lets you record analytics data. The requests hit Segment’s servers, and then Segment routes your data to any destination you want. Get started with the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/). 	
+ 
+
 ## Method compatibility
 
 Not all destinations can accept data from specific method types. To know if a destination can accept data from specific method types, look for the *Quick Info* box at the top of the destination's documentation page, or check out the [Destinations Methods comparison chart](/docs/connections/destinations/methods-compare/).

src/connections/index.md

@@ -4,15 +4,25 @@ title: Connections Overview
 
 Connections is Segment's core product offering: you can collect event data from your mobile apps, websites, and servers with one API, then pull in contextual data from cloud apps like your CRM, payment systems, and internal databases to build a unified picture of your customers.
 
-## What's a Source?
+## Sources
 
 {% include content/whats-a-source.md %}
 
-## What's a Destination?
+Learn more about sources from the [sources overview page](/docs/connections/sources/).
+
+
+## Destinations
 
 {% include content/whats-a-destination.md %}
 
-## What information can I see on Sources and Destinations pages?
+## Warehouses
+
+{% include content/whats-a-warehouse.md %}
+
+### Reverse ETL
+With [Reverse ETL](/docs/connections/reverse-etl/), your data warehouse acts as your source, enabling you to send data from your warehouse to your destinations. 
+
+## Information on sources and destinations pages
 
 The Sources and Destinations pages allow each user to decide what information appears in their personal view for each page.
 
@@ -40,6 +50,3 @@ You can then sort or filter each column to just the values you care about, by cl
 
 
 
-## What is a Warehouse?
-
-{% include content/whats-a-warehouse.md %}