Merge pull request #201 from segmentio/repo-sync

repo sync

Author: bot-docsteam

.vscode/yml.code-snippets

@@ -21,8 +21,4 @@
 		"body":["- name: ${1:name}\r\tdescription: ${2:description}\r\tdefault: ${3}"],
 		"description": "Yaml settings"
 	},
-	"ext_link":{
-		"prefix": ["{:}"],
-		"body":["{:target='${1:_blank}'}"]
-	},
 }

CONTRIBUTING.md

@@ -10,7 +10,7 @@ Before you begin:
 
 ## Use the contribution links from any docs page
 
-Not all pages have a 1-1 mapping with their location within the repository. This can make browsing and locating the file you're trying to reference a challenge. As you browse [segment.com/docs](https://segment.com/docs), you'll notice two links in the right sidebar, at the top of the page. Click **Edit this page** to open the page in the Github editor. Or, click **Request docs change** to create a new issue that references the page.
+Not all pages have a 1-1 mapping with their location within the repository. This can make browsing and locating the file you're trying to reference a challenge. As you browse [segment.com/docs](https://segment.com/docs), you'll notice two links in the right sidebar, at the top of the page. Click **Edit this page** to open the page in the GitHub editor. Or, click **Request docs change** to create a new issue that references the page.
 
 ## Want to go deeper? Fork the repository
 
@@ -39,7 +39,7 @@ The most interesting ones are:
 
 ### Images
 
-**Save all images locally! No linking to 3rd party-hosted images!** Images are published to our CDN from the build step, and this means they won't go missing if the hosting service dujour goes out of business.
+**Save all images locally! No linking to third-party hosted images!** Images are published to our CDN from the build step, and this means they won't go missing if the hosting service dujour goes out of business.
 
 There are no _enforced_ naming conventions at this time. Files that start with an underscore are ignored by Jekyll. Anything you see with `asset` was dowloaded by a script to migrate it out of Contents.io.
 
@@ -77,11 +77,11 @@ 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).
 
-### Frontmatter
+### Front matter
 
-Each Markdown file in the docs can have "frontmatter" associated with it at the top of the file. These are considered by Jekyll to be "properties" of a page, generally control how the HTML page is built or rendered.
+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.
 
-Frontmatter in a file will look something like this:
+Front matter in a file will look something like this:
 
 ```md
 ---
@@ -90,25 +90,25 @@ hide-feedback: false
 ---
 ```
 
-Each piece of frontmatter does something special!
+Front matter variables have unique functions, including the following:
 
-#### Content-related frontmatter
+#### Content-related front matter
 - `beta`: default false. When true, show an "in beta" warning in the page layout (see the warning in `_includes/content/beta-note.md`)
-- `rewrite`: defaults to false. This is a legacy frontmatter flag that comes from the old `site-docs` repo, and which labels any destination that was rewritten in ~2018 to a standardized template. It disables the duplicate "connection modes" table that would otherwise show up in the boilerplate content at the end of the page.
+- `rewrite`: defaults to false. This is a legacy front matter flag that comes from the old `site-docs` repo, and which labels any destination that was rewritten in ~2018 to a standardized template. It disables the duplicate "connection modes" table that would otherwise show up in the boilerplate content at the end of the page.
 - `hide-dossier`: defaults to false. When true, hides the "quick info" box at the top of a destination page.
 - `hide-boilerplate`: defaults to false. When true, none of the content from `destination-footer.md` is appended to the destination page.
 - `hide-cmodes`: defaults to false. A renaming of "rewrite" for more clarity, hides the connection modes table in the boilerplate.
 - `hide-personas-partial`: defaults to false. When true, hides the section of content from `destination-footer.md` that talks about being able to receive personas data.
 - `integration_type`: This is set in the `_config.yml` on three paths to add a noun (Source, Destination, or Warehouse) to the end of the title, and the end of the title tag in the html layout. It also controls the layout and icon for some of these.
 - `source-type`: These are only used to supplement when a Cloud App in the sources path doesn't appear in the Config API list, and needs its type explicitly set. It runs some logic in the `cloud-app-note.md` to explain which cloud-apps are object vs event sources.
 
-#### Utility frontmatter
+#### Utility front matter
 - `published`: defaults to true. Set this to "false" to prevent Jekyll from rendering an HTML page for this file. Good for when you're working on something in the repo but aren't ready to release it yet, and don't want to use a Draft PR.
 - `hidden`: omits the file from the `sitemap.xml`, adds a `<meta name="robots" content="noindex" />` to the top of the generated HTML file, and drops it from the convenience script for regenerating the nav.
 - `hide-sidebar`: defaults to false. When true, hide the entire right-nav sidebar. Use with `hide-feedback` if you want to disable *all* feedback affordances.
 - `hide-feedback`: defaults to false. When true, hide the feedback in both rnav and footer. Good for landing pages.
 - `hide_toc`: hides the right-nav TOC that's generated from H2s. Also good for landing pages.
 - `landing`: defaults to false. Use this to drop the noun set by `integration_type` from the tab title.
-- `redirect_from`: Defaults to null. Takes an array of URLs from the frontmatter 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.
+- `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

src/_includes/content/destination-footer.md

@@ -20,28 +20,6 @@ When you first create an audience, Personas sends an Identify call for every use
 
 {% endif %}
 
-{% unless page.rewrite == true or page.hide-cmodes == true%}
-## Supported Sources and Connection Modes
-{% if currentIntegration.components.size > 0 %}
-{% include content/connection-modes.md %}
-
-{% endif %}
-
-{% if currentIntegration.browserUnbundlingSupported == true and currentIntegration.browserUnbundlingPublic == true %}
-  Segment offers an optional **Cloud-based** Connection Mode for **Web** data with {{ currentIntegration.display_name }}. As a reminder, this removes the {{ currentIntegration.display_name }} javascript library from your site, improving performance.
-{% endif %}
-
-{% unless page.hide-device == true %}
-{% if currentIntegration.platforms.mobile == true %}
-  {% if currentIntegration.platforms.server == true %}
-  Segment offers an *optional* **Device-based** Connection Mode for **Mobile** data going to {{ currentIntegration.display_name }}, so that you can use {{ currentIntegration.display_name }} features that collect data directly from the mobile device. To do this, you must package the Segment-{{ currentIntegration.display_name }} mobile SDK with the Segment mobile library.
-  {% else %}
-  This destination *requires* that you use a **Device-based** Connection Mode for **Mobile** data. Make sure you package the {{ currentIntegration.display_name }} mobile SDK with the Segment mobile library.
-  {% endif %}
-{% endif %}
-{% endunless %}
-{% endunless %}
-
 {% unless page.hide-settings == true %}
 ## Settings
 Segment lets you change these destination settings from the Segment app without having to touch any code.

src/_includes/content/source-region-unsupported.md

@@ -0,0 +1,9 @@
+<div class="premonition warning">
+  <div class="fa fa-check-square"></div>
+  <div class="content">
+    <p class="header">This {{ page.integration_type }} is supported in US data processing regions.</p>
+    <p markdown=1>
+      The {{ page.title | replace: 'Source', '' }} source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see [Regional Segment](/docs/guides/regional-segment/).
+    </p>
+  </div>
+</div>