Merge branch 'new-docs' of git.int.sfo01.mml:mxml/api-spec into new-docs

Author: mthurman

content/docs/guides/create-a-post.md

@@ -8,9 +8,6 @@ title: "Create a Post"
 
 A [Post](/reference/resources/post) is the microblogging primitive of the App.net API. When a user creates a post, it appears in all of their follower's streams. Posts can have images, links, and annotations but at their simplest, they just contain a piece of text.
 
-* TOC
-{:toc}
-
 ## Create a post
 
 The easiest way to create a post is to use [one of the API libraries](/docs/libraries).

content/docs/guides/create-an-app.md

@@ -6,9 +6,6 @@ title: "Create an App"
 
 To start accessing parts of the API that require authentication you will need an **access token**. The easiest way to create an access token is to register an app in your [account dashboard](https://account.app.net/settings/).
 
-* TOC
-{:toc}
-
 ## Creating an App
 
 1. Start by visiting [account.app.net/settings/](https://account.app.net/settings/). Click on "[Your Apps](https://account.app.net/developer/apps/)" in the bottom left hand corner to go to Your Apps Dashboard.

content/docs/guides/messaging.md

@@ -4,9 +4,6 @@ title: "Messaging Overview"
 
 # App.net Messaging
 
-* TOC
-{:toc}
-
 The App.net Messaging API allows a User to create public, private, semi-private  messages between an arbitrary number of users. If you'd like to create public messages that your App.net followers see in their streams, you should [create a post](/reference/resources/post/lifecycle/#create-a-post) with the Stream API. If you need a more flexible messaging solution, the Messaging API is for you.
 
 Our messaging API is built around 2 central objects: [Channels](/reference/resources/channel/) and [Messages](/reference/resources/message/). If you're familiar with the App.net Stream API, here are some analogies:

content/docs/guides/send-a-broadcast.md

@@ -10,9 +10,6 @@ Broadcast Channels are designed to carry low-volume, high-value updates of inter
 
 Just a reminder: while you can do all of this using our API, you don't have to. We have [tools for publishers](https://broadcast.app.net/manage/) to help you quickly get started pulling content in from elsewhere on the web, and you can send them manually via the web or the App.net iOS and Android apps. To get started, **we recommend that you create and set up your broadcast channel with [our web publisher tools](https://broadcast.app.net/manage/)** and only use the API to send broadcasts via the channel you created.
 
-* TOC
-{:toc}
-
 ## Send a Broadcast
 
 There are a number of parts to each broadcast message. To illustrate, here's a screenshot of a broadcast in the App.net iOS app:

content/docs/libraries.md

@@ -6,9 +6,6 @@ title: "API Libraries"
 
 Using one of the following libraries will help you get up and running with the App.net API in no time. Most of these libraries are maintained by the community.
 
-* TOC
-{:toc}
-
 ## Python
 
     pip install adnpy

content/reference/index.md

@@ -5,9 +5,6 @@ title: "App.net API Reference"
 
 These pages contain the complete specification of how the App.net API works. We try to follow standard practices to make our API easy to use from one of our [client libraries](/docs/libraries/) or from any normal HTTP client.
 
-* TOC
-{:toc}
-
 ## Authentication
 
 We use the [OAuth 2.0 protocol](http://tools.ietf.org/html/rfc6749) to authenticate clients to the API. There are multiple ways to get a token to a user's account. Please read our [Authentication Overview](/reference/authentication/) to choose the right one for your app.

static/css/style.css

@@ -151,7 +151,6 @@ code {
 }
 
 #markdown-toc {
-    display: none;
     color: #ddd;
     margin: 0 0 30px 0;
     padding: 10px 0 0 25px;