Add context!!! (#1044)

Author: sanscontext

src/connections/sources/catalog/libraries/mobile/android/index.md

@@ -106,6 +106,9 @@ Ensure that the necessary permissions are declared in your application's `Androi
 
 ## Identify
 
+> note ""
+> **Good to know**: For any of the different methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
+
 `identify` lets you tie a user to their actions and record traits about them.  It includes a unique User ID and any optional traits you know about them.
 
 We recommend calling `identify` a single time when the user's account is first created, and only identifying again later when their traits change.

src/connections/sources/catalog/libraries/mobile/android/quickstart.md

@@ -3,20 +3,31 @@ title: 'Quickstart: Android'
 hidden: true
 ---
 
-<!-- LR 4/21/2020: TODO: none of the quickstarts actually walk you through creating the source in the workspace -->
-
-
 [![Maven Central](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.android/analytics/badge.svg)](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.android/analytics)
 
 This tutorial will help you start sending analytics data from your Android app to Segment and any of our destinations, using our Android library. As soon as you're set up you'll be able to turn on any new destinations with the flip of a switch!
 
 If you want to dive deeper at any point, check out the [Android Source Reference](/docs/connections/sources/catalog/libraries/mobile/android).
 
-## Step 1: Install the Library
+## Step 1: Create a Source in the Segment app
+
+Before you begin, you need a Workspace (which is a container that holds all of the sources and destinations which are billed together for an organization). If you already created one, great! If not, you can sign up for a free Segment account and create one.
+
+Next, create an Android source from your Workspace:
+
+1. Click **Add Source**.
+2. From the source catalog page, click **Android**.
+3. Click **Add Source** again from the informational panel that appears to the right.
+4. Give the source a display name, and enter the URL the source will collect data from.
+
+When you create a Source in the Segment web app, it tells the Segment servers that you'll be sending data from a specific source type. When you create (or change!) a Source in the Segment app, Segment generates a new Write Key for that source. You use the write key in your code to tell the Segment servers where the data is coming from, so Segment can route it to your destinations and other tools.
+
+
+## Step 2: Install the Library
 
 The recommended way to install the library for Android is with a build system like Gradle. This makes it simple to upgrade versions and add destinations. The library is distributed using [Maven Central](http://maven.org/). Simply add the `analytics` SDK to your module's `build.gradle` file:
 
-```
+```java
 dependencies {
   implementation 'com.segment.analytics.android:analytics:4.+'
 }
@@ -32,7 +43,7 @@ In those cases, you'll need to take some additional steps as shown in the [libra
 
 Now that the SDK is installed and setup, you're ready to...
 
-## Step 2. Initialize the Client
+## Step 3. Initialize the Client
 
 We recommend initializing the client in your `Application` subclass.
 ```java
@@ -47,11 +58,11 @@ Analytics.setSingletonInstance(analytics);
 ```
 
 **Notes**:
-- Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and is optional, but highly recommended to hit the ground running with core events! See [below](/docs/connections/sources/catalog/libraries/mobile/android/quickstart/#step-5-track-actions) for more info!
+- Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and is optional, but highly recommended to hit the ground running with core events! See [below](/docs/connections/sources/catalog/libraries/mobile/android/quickstart/#step-6-track-actions) for more info!
 - This only installs the Segment destination. This means that all your data will be sent server side to tools.
 If you need to bundle additional destinations client side, you'll need to take some additional steps as [shown here](/docs/connections/sources/catalog/libraries/mobile/android/#about-mobile-connection-modes).
 
-## Step 3. Add Permissions
+## Step 4. Add Permissions
 
 Ensure that the necessary permissions are declared in your application's `AndroidManifest.xml`.
 
@@ -63,7 +74,10 @@ Ensure that the necessary permissions are declared in your application's `Androi
 </manifest>
 ```
 
-## Step 4. Identify Users
+## Step 5. Identify Users
+
+> note ""
+> **Good to know**: For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 The `identify` method is one of our core API methods. It's how you tie one of your users and their actions to a recognizable userId. It also lets you record traits about the user, like their email, name, account type, etc. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/mobile/android#identify).
 
@@ -81,7 +95,7 @@ That's identifying Michael by his unique User ID (the one you know him by in you
 
 Once you've added an `identify` call, you're ready to move on to...
 
-## Step 5. Track Actions
+## Step 6. Track Actions
 
 The track method is how you record any actions your users perform. Each action is known by a name, like "Purchased a T-Shirt". You can also record properties specific to those actions. You can read more about `track` in the [track reference](/docs/connections/sources/catalog/libraries/mobile/android#track).
 

src/connections/sources/catalog/libraries/mobile/ios/index.md

@@ -41,7 +41,7 @@ configuration.recordScreenViews = YES; // Enable this to record screen views aut
 [SEGAnalytics setupWithConfiguration:configuration];
 ```
 
-**Note:** Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views is optional using initialization config parameters, but highly recommended to hit the ground running with core events! See [below](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#step-3-track-actions) for more info!
+**Note:** Automatically tracking lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views is optional using initialization config parameters, but highly recommended to hit the ground running with core events! See [below](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#step-4-track-actions) for more info!
 
 And of course, import the SDK in the files that you use it with:
 
@@ -131,6 +131,9 @@ You can also manually `flush` the queue:
 
 Now that the Segment SDK and any accompanying packaged SDKs are installed, you're ready to collect some data!
 
+> note ""
+> **Good to know**: For any of the different methods described in this doc, you can replace the properties and traits in the code samples with variables that represent the data collected.
+
 ### Identify
 
 `identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.

src/connections/sources/catalog/libraries/mobile/ios/quickstart.md

@@ -10,7 +10,20 @@ If you want to dive deeper at any point, check out the [iOS Library Reference](/
 _Note: At the moment Segment does not support tracking watchkit extensions for the Apple watch. [Contact us](https://segment.com/help/contact) if you're interested in a watchkit SDK. For now we recommend tracking watch interactions using the native iPhone app code._
 
 
-## Step 1: Install the SDK
+## Step 1: Create a Source in the Segment app
+
+Before you begin, you need a Workspace (which is a container that holds all of the sources and destinations which are billed together for an organization). If you already created one, great! If not, you can sign up for a free Segment account and create one.
+
+Next, create an iOS source from your Workspace:
+
+1. Click **Add Source**.
+2. From the source catalog page, click **iOS**.
+3. Click **Add Source** again from the informational panel that appears to the right.
+4. Give the source a display name, and enter the URL the source will collect data from.
+
+When you create a Source in the Segment web app, it tells the Segment servers that you'll be sending data from a specific source type. When you create (or change!) a Source in the Segment app, Segment generates a new Write Key for that source. You use the write key in your code to tell the Segment servers where the data is coming from, so Segment can route it to your destinations and other tools.
+
+## Step 2: Install the SDK
 
 The recommended way to install Analytics for iOS is using [Cocoapods](http://cocoapods.org), since it means you can create a build with specific bundled destinations, and because it makes it simple to install and upgrade.
 
@@ -50,7 +63,10 @@ In those cases, follow the additional steps to [bundle the destination tools](/d
 
 Now that the SDK is installed and set up, you're ready to start making calls!
 
-## Step 2: Identify Users
+## Step 3: Identify Users
+
+> note ""
+> **Good to know**: For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 The `identify` method is how you tell Segment who the current user is. It takes a unique User ID, and any optional traits you know about them. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/mobile/ios#identify).
 
@@ -68,7 +84,7 @@ That call identifies Michael by his unique User ID (`f4ca124298`, which is the o
 
 Once you've added an `identify` call, you're ready to move on to tracking!
 
-## Step 3: Track Actions
+## Step 4: Track Actions
 
 The `track` method is how you tell Segment about the actions your users are performing in your app. Every action triggers what we call an "event", which can also have associated properties. You can read more about `track` in the [track method reference](/docs/connections/sources/catalog/libraries/mobile/ios#track).
 
@@ -101,7 +117,7 @@ That tells us that your user triggered the **Signed Up** event, and chose your h
 
 Once you've added a few `track` calls, **you're set up!** You successfully instrumented your app, and can turn on any destination you like from your Segment workspace. However, there are a few important things to know about for mobile app instrumentation, so read on!
 
-## Step 4: Flushing
+## Step 5: Flushing
 
 By default, Segment sends ("flushes") events from the iOS library in batches of `20`, however this is configurable. You can set the `flushAt` value to change the batch size, or you can set it to `1` to disable batching completely.
 
@@ -121,7 +137,7 @@ You can also manually call `flush` in your code to send all the messages in the
 [[SEGAnalytics sharedAnalytics] flush]
 ```
 
-## Step 5: Submitting to the App Store
+## Step 6: Submitting to the App Store
 
 Segment collects the IDFA of the user's device to use in mobile install attribution with destinations like Mobile App Tracking.
 

src/connections/sources/catalog/libraries/server/go/index.md

@@ -42,6 +42,9 @@ The default initialization settings are production-ready and queue 20 messages b
 
 ## Identify
 
+> note ""
+> **Good to know**: For any of the different methods described on this page, you can replace the properties and traits in the code samples with variables that represent the data collected.
+
 `identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.
 
 We recommend calling `identify` a single time when the user's account is first created, and only identifying again later when their traits change.
@@ -434,7 +437,7 @@ client.Enqueue(analytics.Track{
     SetCategory("Enterprise").
     Set("application", "Segment Desktop"),
 })
-```  
+```
 
 ```go
 client.Enqueue(analytics.Track{
@@ -445,7 +448,7 @@ client.Enqueue(analytics.Track{
     "application": "Segment Desktop",
   },
 })
-```  
+```
 
 Lastly, you'll notice that configuration is provided during initialization and cannot be changed after initialization. The various configuration options are documented in the [GoDocs](https://godoc.org/gopkg.in/segmentio/analytics-go.v3#Config).
 

src/connections/sources/catalog/libraries/server/go/quickstart.md

@@ -8,8 +8,21 @@ This tutorial will help you start sending data from your Go servers to Segment a
 
 If you want to dive deeper at any point, check out the [Go library reference](/docs/connections/sources/catalog/libraries/server/go/).
 
+## Step 1: Create a Source in the Segment app
 
-## Step 1: Install the Package
+Before you begin, you need a Workspace (which is a container that holds all of the sources and destinations which are billed together for an organization). If you already created one, great! If not, you can sign up for a free Segment account and create one.
+
+Next, create a Go source from your Workspace:
+
+1. Click **Add Source**.
+2. From the source catalog page, click **Go**.
+3. Click **Add Source** again from the informational panel that appears to the right.
+4. Give the source a display name, and enter the URL the source will collect data from.
+
+When you create a Source in the Segment web app, it tells the Segment servers that you'll be sending data from a specific source type. When you create (or change!) a Source in the Segment app, Segment generates a new Write Key for that source. You use the write key in your code to tell the Segment servers where the data is coming from, so Segment can route it to your destinations and other tools.
+
+
+## Step 2: Install the Package
 
 Installing our Go library is easy, just run the following:
 
@@ -32,7 +45,10 @@ func main() {
 That will create a `client` that you can use to send data to Segment for your source. Once you've got that, you're ready to...
 
 
-## Step 2: Identify Users
+## Step 3: Identify Users
+
+> note ""
+> **Good to know**: For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 The `identify` method is how you tell Segment who the current user is. It includes a unique User ID and any optional traits you know about them. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/server/go#identify).
 
@@ -56,7 +72,7 @@ When you're using our Go library, you don't need to identify a user on every req
 Once you've added an identify call, you can move on to...
 
 
-## Step 3: Track Actions
+## Step 4: Track Actions
 
 The `track` method is how you tell Segment about which actions your users are performing. Every action triggers what we call an "event", which can also have associated properties. You can read more about `track` in the [track reference](/docs/connections/sources/catalog/libraries/server/go#track).
 

src/connections/sources/catalog/libraries/server/go/v2/quickstart.md

@@ -7,8 +7,20 @@ This tutorial will help you start sending data from your Go servers to Segment a
 
 If you want to dive deeper at any point, check out the [Go library reference](/docs/connections/sources/catalog/libraries/server/go/).
 
+## Step 1: Create a Source in the Segment app
 
-## Step 1: Install the Package
+Before you begin, you need a Workspace (which is a container that holds all of the sources and destinations which are billed together for an organization). If you already created one, great! If not, you can sign up for a free Segment account and create one.
+
+Next, create a Go source from your Workspace:
+
+1. Click **Add Source**.
+2. From the source catalog page, click **Go**.
+3. Click **Add Source** again from the informational panel that appears to the right.
+4. Give the source a display name, and enter the URL the source will collect data from.
+
+When you create a Source in the Segment web app, it tells the Segment servers that you'll be sending data from a specific source type. When you create (or change!) a Source in the Segment app, Segment generates a new Write Key for that source. You use the write key in your code to tell the Segment servers where the data is coming from, so Segment can route it to your destinations and other tools.
+
+## Step 2: Install the Package
 
 Installing our Go library is easy, just run the following:
 
@@ -31,7 +43,10 @@ func main() {
 That will create a `client` that you can use to send data to Segment for your source. Once you've got that, you're ready to...
 
 
-## Step 2: Identify Users
+## Step 3: Identify Users
+
+> note ""
+> **Good to know**: For any of the different methods described in this quickstart, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
 The `identify` method is how you tell Segment who the current user is. It includes a unique User ID and any optional traits you know about them. You can read more about it in the [identify reference](/docs/connections/sources/catalog/libraries/server/go#identify).
 
@@ -56,7 +71,7 @@ When you're using our Go library, you don't need to identify a user on every req
 Once you've added an identify call, you can move on to...
 
 
-## Step 3: Track Actions
+## Step 4: Track Actions
 
 The `track` method is how you tell Segment about which actions your users are performing. Every action triggers what we call an "event", which can also have associated properties. You can read more about `track` in the [track reference](/docs/connections/sources/catalog/libraries/server/go#track).
 

src/connections/sources/catalog/libraries/server/java/index.md

@@ -62,6 +62,9 @@ The following examples use [Guava's](https://github.com/google/guava) immutable
 
 ## Identify
 
+> note ""
+> **Good to know**: For any of the different methods described on this page, you can replace the properties and traits in the code samples with variables that represent the data collected.
+
 `identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.
 
 We recommend calling `identify` a single time when the user's account is first created, and only identifying again later when their traits change.