Pb adops edits (#1214)

* Made edit changes

* Removed action item.

* fixed spacing on bulleted list

* Updating alert

* added alerts to includes

* Updated intro

* Fixed alerts and toc

_includes/alerts/alert_important.html

@@ -0,0 +1 @@
+<div markdown="span" class="pb-alert pb-alert-important" role="alert"><i class="fa fa-exclamation-circle"></i> <b>Important:</b> {{include.content}}</div>

_includes/alerts/alert_note.html

@@ -0,0 +1 @@
+<div markdown="span" class="pb-alert pb-alert-note" role="alert"><i class="fa fa-info-circle"></i> <b>Note:</b> {{include.content}}</div>

_includes/alerts/alert_tip.html

@@ -0,0 +1 @@
+<div markdown="span" class="pb-alert pb-alert-tip" role="alert"><i class="fa fa-check-circle"></i> <b>Tip:</b> {{include.content}}</div>

_includes/alerts/alert_warning.html

@@ -0,0 +1 @@
+<div markdown="span" class="pb-alert pb-alert-warning" role="alert"><i class="fa fa-exclamation-triangle"></i> <b>Warning:</b> {{include.content}}</div>

_includes/send-all-bids-keyword-targeting.md

@@ -1,5 +1,9 @@
-{: .alert.alert-info :}
+{% capture infoNote %}
 **Important:** DFP has a key-value key character [limit](https://support.google.com/dfp_premium/answer/1628457?hl=en#Key-values) of up to **20 characters**. Some of the keys without truncation will exceed 20 chars. Prebid.js automatically truncates the key length to 20 characters. For example, `hb_adid_longBidderName` is truncated to `hb_adid_longBidderNa` (`me` is truncated). Note that the key is case-sensitive. To get the exact key-value keys for each bidder, find them at [Bidder Params](/dev-docs/bidders.html).
+{% endcapture %}
+
+{% include alerts/alert_note.html content=infoNote %}
+
 
 {: .table .table-bordered .table-striped }
 | Default Key   | Scope    | Description                                                                                     | Example   |

adops/before-you-start.md

@@ -11,20 +11,22 @@ sbUUID: 3.2
 
 
 
-# Ad Operations View of Prebid
+# Ad Ops and Prebid
 {: .no_toc }
 
-There are a number of things you need to understand and to decide before implementing any flavor of Prebid.
+Prior to implementing Prebid, whether that is Prebid.js, Prebid Server or Prebid Mobile, a publisher will need to set up their price granularity and line item configurations. 
 
-This page has information about considerations of your Prebid setup such as price granularity, line item configuration, and more.
 
-{: .alert.alert-info :}
+{% capture infoNote %}
 This page assumes you have read [Getting Started with Prebid.js]({{site.baseurl}}/overview/getting-started.html), though it applies to Prebid SDK and Server as well.
+{% endcapture %}
+
+{% include alerts/alert_note.html content=infoNote %}
 
 * TOC
 {: toc }
 
-### Step 1. Decide on price bucket granularity
+### Decide on price bucket granularity
 
 With pre-bid, you'll need to setup line items to tell your ad server how much money the “bidder” demand is worth to you. This process is done via key-values.
 
@@ -38,12 +40,10 @@ Example:
 
 Our recommendation is to start with $1 or 10 cent granularity until you're more comfortable with Prebid.js. At $1, you only need to setup 10-20 line items – easy. When you're ready, get more granular with the price buckets to improve yield.
 
-Note that DFP has an order [object limits](https://support.google.com/dfp_premium/answer/1628457?hl=en#Trafficking) of containing up to 450 line items (including archived line items). If you are designing your own granularity setup, make sure you do not exceed that amount. Or, you can find the recommended pre-configured granularities [here](/dev-docs/publisher-api-reference.html#module_pbjs.setPriceGranularity).
+Note that DFP has an order [object limits](https://support.google.com/dfp_premium/answer/1628457?hl=en#Trafficking) of containing up to 450 line items (including archived line items). If you are designing your own granularity setup, make sure you do not exceed that amount. Or, you can find the recommended pre-configured granularities in our API reference under the [Set Config Price Granularity instructions](/dev-docs/publisher-api-reference.html#setConfig-Price-Granularity).
 
-{: .alert.alert-success :}
-**Action Item:** See the [Publisher API Reference](/dev-docs/publisher-api-reference.html#setConfig-Price-Granularity) for more detail.
 
-### Step 2. One set of line items for all bidders vs. a set of line items for each bidder
+### One set of line items for all bidders vs. a set of line items for each bidder
 
 + <a href="#all-bidders">A. One set of line items for all bidders</a>
 + <a href="#per-bidder">B. One set of line items per bidder</a>
@@ -53,15 +53,18 @@ Note that DFP has an order [object limits](https://support.google.com/dfp_premiu
 One set of line items for all bidders is the recommended way of setting up your line items.  Choose this option if you prefer an easier, low-maintenance setup:
 
 - It's quicker and easier to setup, because you only have to create one set of line items.
-
 - It's easier to maintain because adding more bidders requires no change to your line item setup.
-
 - It's less error-prone because you only need to maintain 3 keywords:
 
 {% include default-keyword-targeting.md %} 
 
-{: .alert.alert-success :}
-**Action Item:** For instructions on setting up pre-bid with one set of line items for all bidders, see [Send Top Bid to Ad Server - Step by Step guide to DFP setup](/adops/step-by-step.html).
+
+{% capture successNote %}
+For instructions on setting up pre-bid with one set of line items for all bidders, see [Send Top Bid to Ad Server - Step by Step guide to DFP setup](/adops/step-by-step.html).
+{% endcapture %}
+
+{% include alerts/alert_tip.html content=successNote %}
+
 
 #### One set of line items for each bidder <a name="per-bidder"/>
 
@@ -73,18 +76,21 @@ Choose one set of line items for each bidder if you:
 - Require bid landscape data for header bidding partners
     - With one set of line items for all bidders, Prebid.js sends the bidder information (Which bidder has the highest price) via a keyword `bidder=bidder_name`. To run a report to attribute winning bids to bidders, you will need to rely on your ad server's keyword reports. DFP supports this, but some ad servers do not. DFP does not support running reports for more than 2 keywords. Therefore, if you have existing reports that already rely on keywords, and you want to add a winning bid by bidder dimension, use one set of line items for each bidder.
 
-- Requires setting more keyword targeting within your ad server. The below keys are targeting are required for each of your header bidding partner.
+- Requires setting more keyword targeting within your ad server. The table below lists the required and optional keys for targeting with each of your header bidder partners.
 
 {% include send-all-bids-keyword-targeting.md %} 
 
-{: .alert.alert-success :}
-**Action Item:** For instructions on setting up pre-bid with one set of line items for each bidder, see [Send all bids to the ad server - Ad Ops setup](/adops/send-all-bids-adops.html).
+{% capture successNote %}
+For instructions on setting up pre-bid with one set of line items for each bidder, see [Send all bids to the ad server - Ad Ops setup](/adops/send-all-bids-adops.html).
+{% endcapture %}
+
+{% include alerts/alert_tip.html content=successNote %}
 
-### Step 3. Work together with your dev team
+### Work together with your dev team
 
 Implementing header bidding requires much more collaboration with your dev team than normal Ad Ops setup. For example:
 
-- Setting up price granularity requires you and the dev team working together to ensure the price buckets match. We have seen cases when the code on page sends $0.10 increments, while the line item setup expects $0.50 increments. This results in the ad server not catching 80% of the bids.
+> Setting up price granularity requires you and the dev team working together to ensure the price buckets match. We have seen cases when the code on page sends $0.10 increments, while the line item setup expects $0.50 increments. This results in the ad server not catching 80% of the bids.
 
 ## Related Topics
 

assets/css/style.css

@@ -124,6 +124,38 @@ hr {
 	align-items: stretch;
 }
 
+/* alerts */
+.pb-alert { 
+
+	padding:10px;
+	width: 100%;
+	margin-bottom: 10px;
+}
+
+.pb-alert-note { 
+	background-color: #deecf7;
+	color: #4b6f8d;
+	border: 1px solid #4b6f8d;
+}
+
+.pb-alert-warning { 
+	background-color: #ecdcdd;
+	color: #944644;
+	border: 1px solid #944644;
+}
+
+.pb-alert-important { 
+	background-color: #ecdcdd;
+	color: #464646;
+	border: 1px solid #464646;
+}
+
+.pb-alert-tip { 
+	background-color: #e3efd8;
+	color: #527542;
+	border: 1px solid #527542;
+}
+
 
 /* NavBar */