Merge branch 'master' into DOC-146_Data-Res-Updates

Author: markzegarelli

README.md

@@ -189,9 +189,9 @@ Each piece of frontmatter does something special!
 #### Content-related frontmatter
 - `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.
-- `hide-boilerplate`: defaults to false. When true, none of the content from `integration-foot.md` is appended to the 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 `integration-foot.md` that talks about being able to receive personas data.
+- `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.
 

_config.yml

@@ -25,12 +25,12 @@ defaults:
       path: "connections/destinations/catalog"
     values:
       integration_type: destination
-      layout: integration
+      layout: destination
   - scope:
       path: "connections/sources/catalog"
     values:
       integration_type: source
-      layout: integration
+      layout: source
   - scope:
       path: "connections/storage/catalog"
     values:
@@ -53,4 +53,4 @@ algolia:
   application_id: UINQ2M4D9S
   index_name:     segment-docs
   files_to_exclude:
-    - _release_notes/*
+    - _release_notes/*

devguide.md

@@ -53,15 +53,19 @@ It also does some slugification and destination-name normalization, since our ha
 
 ### Layouts
 
-`default.html` is the base container through which all the individual other layouts (currently one, `page.html`) are built to have the right title, seo, etc. `Integration.html` contains the logic that runs the catalog pages.
+`default.html` is the base container through which all the individual other layouts are built to have the right title, seo, etc. The template inheritance is described in the diagram below.
+
+The `destination.html`, `source.html`, and `integration.html` templates contain the logic that runs the layouts for individual catalog pages. Storage/warehouses use the generic Integration right now because they don't need anything special. Set the layout in the Jekyll `_config.yml` file.
 
 ```text
 default.html
- |- integration.html
- |- catalog.html
- |- main.html
-    |-page.html
-    |-home.html
+  |- integration.html
+    |- destination.html
+    |- source.html
+  |- main.html
+    |- catalog.html
+    |- home.html
+    |- page.html
 ```
 
 ### Platform Config API + Catalog

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2021-03-10 
+# destination categories last updated 2021-03-29 
 items:
 - display_name: Email Marketing
   slug: email-marketing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-03-10 
+# destination data last updated 2021-03-29 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -13672,6 +13672,26 @@ items:
       required: false
       description: Map your Segment properties to the Marketo Activity Fields
       settings:
+      - name: marketoAttributeType
+        display_name: Marketo Field Type
+        type: SELECT
+        deprecated: false
+        required: true
+        select_validators:
+          select_options:
+          - string
+          - boolean
+          - number
+          - date
+        description: Enter the Marketo Field type.
+        settings: []
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as the Primary field in Marketo.
+        settings: []
       - name: segmentProperty
         display_name: Segment Property Name
         type: STRING
@@ -13694,26 +13714,6 @@ items:
           Enter the Marketo Field name. Make sure to copy and paste the exact
           API Name for your field as it appears in Marketo.
         settings: []
-      - name: marketoAttributeType
-        display_name: Marketo Field Type
-        type: SELECT
-        deprecated: false
-        required: true
-        select_validators:
-          select_options:
-          - string
-          - boolean
-          - number
-          - date
-        description: Enter the Marketo Field type.
-        settings: []
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as the Primary field in Marketo.
-        settings: []
     - name: event
       display_name: Segment Event Name
       type: STRING
@@ -16689,6 +16689,59 @@ items:
       server: false
   previous_names:
   - Pingdom
+- display_name: Pinterest Audiences
+  slug: pinterest-audiences
+  name: catalog/destinations/pinterest-audiences
+  description: >-
+    The Pinterest Audiences integration lets you add user audiences for
+    remarketing.
+  hidden: false
+  url: connections/destinations/catalog/pinterest-audiences
+  status: PUBLIC
+  logo:
+    url: 'https://cdn.filepicker.io/api/file/p3vCawmQ2CtnbacRnRHD'
+  mark:
+    url: 'https://cdn.filepicker.io/api/file/GBX5NV3USYmSOcpePkA1'
+  categories:
+  - Advertising
+  components:
+  - type: CLOUD
+  platforms:
+    browser: false
+    server: true
+    mobile: false
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: true
+  methods:
+    alias: false
+    group: false
+    identify: false
+    page_view: false
+    track: true
+  settings:
+  - name: account
+    display_name: account
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: ^\d+$
+    description: >-
+      You can find your Account ID on the **Account Settings** page of your
+      [Pinterest Ads account](https://ads.pinterest.com/). It should be a series
+      of numbers, like `319762813599`.
+    settings: []
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
+  previous_names:
+  - Pinterest Audiences
 - display_name: Pinterest Tag
   slug: pinterest-tag
   name: catalog/destinations/pinterest-tag

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2021-03-10 
+# source cateogries last updated 2021-03-29 
 items:
 - display_name: Server
   slug: server

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2021-03-10 
+# sources last updated 2021-03-29 
 items:
 - display_name: .NET
   slug: net

src/_includes/content/destination-dossier.md

@@ -0,0 +1,14 @@
+<!-- canary comment -->
+
+<!-- in the file we're pulling from the API, "name" corresponds with the path to the yml blob for a specific destination.-->
+{% assign currentSlug = page.url | split: "/" | last %}
+{% assign currentIntegration = site.data.catalog.destinations.items | where: "slug", currentSlug | first %}
+{% if currentIntegration %}
+<!-- this endif prevents you from showing a dossier if there's no info in destinations.yml-->
+
+
+
+<!-- TODO -->
+
+
+{% endif %}

src/_includes/content/integration-foot.md renamed to src/_includes/content/destination-footer.md

@@ -0,0 +1,19 @@
+---
+layout: integration
+---
+<div class="markdown">
+
+{% unless page.hide-dossier == true %}
+  {% capture destination-dossier %}{% include content/destination-dossier.md  %}{% endcapture %}
+  {{ destination-dossier | markdownify }}
+{% endunless %}
+
+
+  {{ content }}
+
+{% unless page.hide-boilerplate == true %}
+  {% capture destination-footer %}{% include content/destination-footer.md  %}{% endcapture %}
+  {{ destination-footer | markdownify }}
+{% endunless %}
+
+</div>