feat(Docs): Next batch of developer migration (AB test app 1)

src/content/docs/new-relic-solutions/build-nr-ui/build-ab-app/add-charts.mdx

@@ -0,0 +1,26 @@
+---
+title: 'Add chart components to your A/B test application'
+metaDescription: 'Add chart components to your A/B test application'
+freshnessValidatedDate: never
+---
+
+<Callout variant="tip">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up.
+
+Each lesson in the course builds upon the last, so make sure you've completed the last lesson, Serve your New Relic application, before starting this one.
+
+</Callout>
+
+
+The New Relic application that you're building throughout this course allows developers to A/B test their websites. To run a successful A/B test, site owners need to be able to analyze the results. Without knowing how each design performs, how will developers determine which design to use?
+
+Your application displays data for two competing versions. With various charts and tables, your users will be able to analyze the results of their test and make informed decisions on which design will work best to achieve their goals.
+
+You'll refer back to this mockup many times throughout this course. It shows you what charts to create, how to organize them, and what kind of data to provide them. In the next four sections, you learn how to create every chart that your A/B test application needs to operate effectively. After that, you'll arrange the charts to match the mockup's design and supply New Relic data collected from the demo applications you spun up earlier.
+
+<Callout variant="tip">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up. Continue on to the next lesson: Add your first chart.
+
+</Callout>

src/content/docs/new-relic-solutions/build-nr-ui/build-ab-app/add-ui.mdx

@@ -0,0 +1,23 @@
+---
+title: 'Add user interface components to your application'
+metaDescription: 'Add user interface components to your application'
+freshnessValidatedDate: never
+---
+
+<Callout variant="tip">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up. If you haven't already, check out the Overview.
+
+Each lesson in the course builds upon the last, so make sure you've completed the last lesson, Add a chart group, before starting this one.
+
+</Callout>
+
+If an application is organized, it is more readable and more understandable. In your A/B test application, you have a lot of charts, but no organization. In the next few lessons, you'll use user interface components to bring some organization to your application and provide new functionality. First, you'll use a `Grid` component to arrange your charts to match the layout in your design guide. Second, you'll add headings to clarify what each chart represents. Third, you'll add descriptions for your A and B design versions to the top of your app. Finally, you'll create a section for ending your A/B test.
+
+In the next lesson, you arrange your charts to look like they do in your design guide.
+
+<Callout variant="course">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up. When you're ready, continue on to the next lesson: Add a grid.
+
+</Callout>

src/content/docs/new-relic-solutions/build-nr-ui/build-ab-app/chart-group.mdx

@@ -0,0 +1,226 @@
+---
+title: 'Add a chart group'
+metaDescription: 'Add a chart group'
+freshnessValidatedDate: never
+---
+
+<Callout variant="tip">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up. If you haven't already, check out the Overview.
+
+Each lesson in the course builds upon the last, so make sure you've completed the last lesson, Add tables, before starting this one.
+
+</Callout>
+
+
+In previous lessons, you added a variety of charts to your A/B test application. These charts presented different facets of information about your A/B test, and they behaved independently from one other. In this lesson, you'll create a new pair of line charts and learn how to synchronize their behaviors. 
+
+There is a line graph under each of the tables you created in the last lesson. These line graphs show the version-specific response times for newsletter signup requests. Now, you'll build two more line charts, but this time, you'll group them with a `ChartGroup` and specify that their values are measured in milliseconds.
+
+<Steps>
+
+<Step>
+
+Change to the `add-a-chart-group/ab-test` directory of the [coursework repository](https://github.com/newrelic-experimental/nru-programmability-course):
+
+
+
+```sh
+cd nru-programmability-course/add-a-chart-group/ab-test
+```
+
+
+</Step>
+
+<Step>
+
+In `nerdlets/ab-test-nerdlet`, add a new Javascript file named `page-views.js`:
+
+
+
+```sh
+touch page-views.js
+```
+
+
+</Step>
+
+<Step>
+
+In this new file, create a component called `VersionPageViews` to hold a `LineChart`, which shows the number of times a page is viewed:
+
+
+
+```js fileName=nerdlets/ab-test-nerdlet/page-views.js
+import React from 'react';
+import { LineChart } from 'nr1';
+
+export default class VersionPageViews extends React.Component {
+    render() {
+        const versionPageViews = {
+            metadata: {
+                id: `page-views-${this.props.version}`,
+                name: `Version ${this.props.version.toUpperCase()}`,
+                viz: 'main',
+                color: 'blue',
+                units_data: {
+                    y: 'MS'
+                }
+            },
+            data: [
+                { x: 0, y: 10 },
+                { x: 10, y: 13 },
+                { x: 20, y: 11.5 },
+                { x: 30, y: 10 },
+                { x: 40, y: 8.75 },
+                { x: 50, y: 9 },
+            ],
+        }
+        return <LineChart data={[versionPageViews]} fullWidth />
+    }
+}
+```
+
+
+Notice the new attribute in the series' `metadata` fields: `units_data`. This attribute describes the unit type for a specified data axis. In this case, you set the unit type for the y axis to `'MS'`, which stands for milliseconds. Other options for unit types, include: `'PERCENTAGE'`, `'TIMESTAMP'`, and `'BYTES_PER_SECOND'`.
+
+</Step>
+
+<Step>
+
+In your Nerdlet's `index.js` file, import your new component and update your Nerdlet's `render()` method:
+
+
+
+```js
+
+import React from 'react';
+import NewsletterSignups from './newsletter-signups';
+import PastTests from './past-tests';
+import TotalCancellations from './total-cancellations';
+import TotalSubscriptions from './total-subscriptions';
+import VersionPageViews from './page-views';
+import VersionTotals from './totals';
+
+export default class AbTestNerdletNerdlet extends React.Component {
+    render() {
+        return <div>
+            <NewsletterSignups />
+            <TotalSubscriptions />
+            <TotalCancellations />
+            <VersionTotals version='a' />
+            <VersionTotals version='b' />
+            <VersionPageViews version='a' />
+            <VersionPageViews version='b' />
+            <PastTests />
+        </div>
+    }
+}
+
+```
+
+
+</Step>
+
+<Step>
+
+In `index.js`, import `ChartGroup` from `nr1` and group your `VersionPageViews`:
+
+
+
+```js
+import React from 'react';
+import { ChartGroup } from 'nr1';
+import NewsletterSignups from './newsletter-signups';
+import PastTests from './past-tests';
+import TotalCancellations from './total-cancellations';
+import TotalSubscriptions from './total-subscriptions';
+import VersionPageViews from './page-views';
+import VersionTotals from './totals';
+
+export default class AbTestNerdletNerdlet extends React.Component {
+    render() {
+        return <div>
+            <NewsletterSignups />
+            <TotalSubscriptions />
+            <TotalCancellations />
+            <VersionTotals version='a' />
+            <VersionTotals version='b' />
+            <ChartGroup>
+                <VersionPageViews version='a' />
+                <VersionPageViews version='b' />
+            </ChartGroup>
+            <PastTests />
+        </div>
+    }
+}
+
+```
+
+
+Because the tables are conceptually related, as they show contrasting performance metrics over the same timeslice, it makes sense to group them in a `ChartGroup`. This means that the two charts behave synchronously. For example, when you hover over one chart, the other chart shows a hover indicator at the same x coordinate.
+
+</Step>
+
+<Step>
+
+Navigate to the root of your Nerdpack at `nru-programmability-course/add-a-chart-group/ab-test`.
+
+</Step>
+
+<Step>
+
+Generate a new UUID for your Nerdpack:
+
+
+
+```sh
+nr1 nerdpack:uuid -gf
+```
+
+
+Because you cloned the coursework repository that contained an existing Nerdpack, you need to generate your own unique identifier. This UUID maps your Nerdpack to your New Relic account.
+
+</Step>
+
+<Step>
+
+Serve your application locally:
+
+
+
+```sh
+nr1 nerdpack:serve
+```
+
+
+</Step>
+
+<Step>
+
+View your changes in [New Relic](https://one.newrelic.com?nerdpacks=local).
+
+Here, you see the `LineChart` components synchronized in your application.
+
+When you're finished, stop serving your New Relic application by pressing `CTRL+C` in your local server's terminal window.
+
+<Callout variant="tip">
+
+Each of the chart component types you've used in this lesson have had different series configurations. Most chart components share the same `metadata` attributes, like `LineChart` and `PieChart`, but differ in their `data` formats.
+
+It's helpful to be aware of the different `data` formats, for when you create your own charts. 
+
+</Callout>
+
+</Step>
+
+</Steps>
+
+Now your application is filled with charts, but it doesn't look great. The charts are stacked on top of one another in an unhelpful way. In the next lesson, you'll learn about the user interface components from the SDK and how you can use them to organize your charts.
+
+
+<Callout variant="course">
+
+This lesson is part of a course that teaches you how to build a New Relic application from the ground up. When you're ready, continue on to the next lesson: Add user interface components to your application.
+
+</Callout>