From c0c516ba7a6953fdf982a2a698aa42a1bbb60e5d Mon Sep 17 00:00:00 2001
From: Chris Hill-Scott <me@quis.cc>
Date: Fri, 1 Jul 2016 16:46:14 +0100
Subject: [PATCH] Make documentation its own section of the page
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This visually chunks the page up into three parts:
- keys
- service ID
- documentation

Also fixes the documentation link (because it’s not service-specific).
---
 app/templates/views/api-keys.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/app/templates/views/api-keys.html b/app/templates/views/api-keys.html
index 47bbaa1b6..6f1ce19ae 100644
--- a/app/templates/views/api-keys.html
+++ b/app/templates/views/api-keys.html
@@ -57,10 +57,11 @@
     {{ api_key(current_service.id, "Service ID", thing="service ID") }}
   </div>
 
+  <h2 class="heading-small">Documentation</h2>
   <p>
-    API usage is described in the
-    <a href="{{ url_for('.documentation', service_id=current_service.id) }}">
-    API documentation</a>.
+    See the
+    <a href="{{ url_for('.documentation') }}">
+    API documentation</a> for clients and specfications.
   </p>
 
 {% endblock %}