Start migration (#240)

* Checkin: refresh all the easy stuff.

* config api

* spec migration

* raw migration of destinations files

* raw migration of destinations files

* replace old dest filters doc with recently migrated one

Signed-off-by: sanscontext <[email protected]>

* copy raw partials from site-docs

* useful file!

* Pull in guides.

* move bulk data storage to warehouses path.

* reorder guides holy crap

* Revert whoops in partials dir

* merge markdown partials, will rectify last ones Monday

* Migrate handlebars partials to liquid

* Comment out api-example handlebars tool invocations

* Migrate single instance of youtube helper.

* comment out two instances of snippet helper

* Replace removed examples with vanilla js blobs

* formatting typo

* format typo whoops

* Source catalog structure fixed

* fix formatting

* Edits on Cloud source intro

* preemtively fix some links where I can

* image migration for guides about and bps

* image fixes on the usage guides.

* small fixes

* start removing unused frontmatter flags

* restore lost catalog page

* remove unused 'sidebar' frontmatter

* Root guides images fixed

* more image fixes

* More image fixes

* Per Sperandio, these are okay to delete.

* remove links to removed files

* redirect these to spec per sperandio

* First shot at regenerating sidenav

* guides rejiggering

Author: sanscontext

README.md

@@ -24,10 +24,10 @@ You will need to have Docker installed https://docs.docker.com/install/
 - `build`: Builds the site docs. Used by CI to publish the docs to staging and production
 - `catalog`: Pulls in the latest catalog data from the Platform API and saves it in the respective data files. Requires an API key to be passed in env via PLATFORM_API_TOKEN
 - `sidenav`: Builds the side navs for 'main', 'legal', 'api', 'partners' and stores the output in `/src/_data/sidenav-auto/`. This output isn't used for the actual build.
-- `typewritter`: pulls in the current state of the Docs tracking plan for implementing Segment tracking
+- `typewriter`: pulls in the current state of the Docs tracking plan for implementing Segment tracking
 - `seed`: copies all example data files out of the `_templates` directory and puts them in the `_data` directory. Useful if you don't have a way to setup an API key.
 - `clean`: removes all build artifacts
-- `clean-deps`: removes all doownloaded `gems` and `node_modules`
+- `clean-deps`: removes all downloaded `gems` and `node_modules`
 - `deps`: installs the required `gems` and `node_modules`
 - `dev`: runs `jekyll serve` locally with incremental builds. Useful when updating CSS, JS, or content and you don't want to rebuild everytime.
 

src/404.html

@@ -19,7 +19,7 @@
         <div class="page-404">
           <div class="flex">
             <div class="flex__column--12 flex__column--9@xlarge">
-              <h1 class="page-404__heading">The page you were looking for doesn’t exist.</h1>
+              <h1 class="page-404__heading">The page you were looking for doesn't exist.</h1>
               <div class="flex">
                 <div class="flex__column--12 flex__column--10@xlarge markdown">
                   <p>You may have mistyped the address or the page may have moved. Double-check the URL and try again or search the term.</p>

src/_data/catalog/destinations.yml

@@ -11259,7 +11259,7 @@ items:
     string_validators:
       regexp: ''
     description: >-
-      To find your API key, log into Pendo and navigate to “your user name” >
+      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.
@@ -14087,11 +14087,11 @@ items:
     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
+      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
+      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: []
@@ -15264,7 +15264,7 @@ items:
     string_validators:
       regexp: '^[a-zA-Z0-9]*$'
     description: >-
-      Drop in the “Integration Key” into your Segment Settings UI which you can
+      Drop in the "Integration Key" into your Segment Settings UI which you can
       find on https://businessapp.b2b.trustpilot.com/#/ecommerce/segment
     settings: []
   connection_modes:

src/_data/catalog/incompleteDocs.txt

@@ -3,7 +3,8 @@ src/connections/sources/catalog/cloud-apps/airship
 src/connections/sources/catalog/cloud-apps/launchdarkly
 src/connections/sources/catalog/cloud-apps/pendo
 src/connections/sources/catalog/cloud-apps/project
-src/connections/sources/catalog/libraries/website/shopify-by-littledatasrc/connections/destinations/catalog/adlearn-open-platform
+src/connections/sources/catalog/libraries/website/shopify-by-littledata
+src/connections/destinations/catalog/adlearn-open-platform
 src/connections/destinations/catalog/adquick
 src/connections/destinations/catalog/airship
 src/connections/destinations/catalog/amazon-eventbridge

src/_data/glossary.yml

@@ -56,7 +56,7 @@ JSON: |
 Library: |
   A library is a reusable piece of code which acts as a building block for higher level pieces of code. It's the software equivalent of a 'tool'. For instance, take Instagram filters. In the good old days, to take a picture with an interesting filter, you had to adjust the aperture length, the focal length, the exposure and film speed to get the desired effect. But now, you can just use Instagram, and press a button to get the pre-tuned filter that you want. They've packaged those effects in software and made them re-usable.
 
-  The most common use case for this term at Segment is in reference to the libraries people use to send data to our API. [A full list of libraries can be found in our docs](https://segment.com/docs/libraries/). Libraries are either “[Client Side](#Client-Side)” or “[Server Side](#Server-Side)”.
+  The most common use case for this term at Segment is in reference to the libraries people use to send data to our API. [A full list of libraries can be found in our docs](https://segment.com/docs/libraries/). Libraries are either "[Client Side](#Client-Side)" or "[Server Side](#Server-Side)".
 
 Method: |
   A method is programming speak for "an action an object can take". It's a specific type of function that is attached to an object. All of our analytics tracking libraries create `analytics` objects, and then `track`, `identify`, `page`, etc. are methods you can invoke on those objects.
@@ -88,7 +88,7 @@ Schema: |
   In Segment, you can send data to a Warehouse which has a schema based on the types of data you collect and route through Segment, and which updates as the data you collect changes.
 
 Server Side: |
-  Refers to a group of libraries that can send data to Segment.  This could also could refer to people sending data directly to [our API](https://segment.com/docs/libraries/http/) without using a “library”. Usually used in contrast to [Client Side](#Client-Side).
+  Refers to a group of libraries that can send data to Segment.  This could also could refer to people sending data directly to [our API](https://segment.com/docs/libraries/http/) without using a "library". Usually used in contrast to [Client Side](#Client-Side).
 
   *Server-side libraries* run on a server and are completely invisible to end users. Find the full list of server-side languages Segment supports [in our docs](https://segment.com/docs/libraries/#server). These libraries can be used to track a user in realtime as they use your app, but are also able to run batches of calls to update many end users at once. Server-side libraries do not maintain "state" which means every API call you make must include every detail you want to see inside of Segment.
 

src/_data/landing.yml

@@ -1,12 +1,12 @@
-- name: Guides
+- name: Getting Started
   icon: icon-guides.svg
   description: "Start here! Best practices, Setup steps, and other useful information."
   path: /guides/
 
-- name: Academy
+- name: How-to Guides
   icon: icon-academy.svg
   description: "Learn more about the 'whys' and 'hows' of analytics. A great read if you're just getting started."
-  path: /academy/
+  path: /guides/best-practices/
 
 - name: App
   icon: icon-app.svg

src/_data/sidenav/_auto/legal.yml

@@ -5,6 +5,8 @@ sections:
     title: Terms of Service
   - path: /legal/acceptable-use-policy
     title: Acceptable Use Policy
+  - path: /legal/enhanced-onboarding-support
+    title: Enhanced Onboarding Support
   - path: /legal/first-access-beta-preview
     title: First-Access and Beta Preview
   - path: /legal/partnersagreement
@@ -35,7 +37,5 @@ sections:
     title: Terms of Service - 2017
   - path: /legal/terms-updates
     title: Updates - Terms of Service
-  - path: /legal/terms
-    title: Terms of Service
   - path: /legal/website-data-collection-policy
     title: Website Data Collection Policy