app/templates/views/api/index.html

{% extends "withnav_template.html" %}
{% from "components/table.html" import list_table, field, hidden_field_heading %}
{% from "components/api-key.html" import api_key %}

{% block page_title %}
  API integration – GOV.UK Notify
{% endblock %}

{% block maincolumn_content %}

  <h1 class="heading-large bottom-gutter">
    API integration
  </h1>

  <nav class="grid-row">
    <div class="column-half">
      <a class="pill-separate-item" href="{{ url_for('.api_keys', service_id=current_service.id) }}">API keys</a>
    </div>
    <div class="column-half">
      <a class="pill-separate-item" href="{{ url_for('.api_documentation', service_id=current_service.id) }}">Documentation</a>
    </div>
  </nav>

{% endblock %}
-												Add an index page for the API integration

This commit adds a placeholder page which, for now, just has links to
the API keys page and links to the clients.

There’s more stuff to come on this page, but this commit just does the
reorganising so that it’s easier to review.

											
										
										
											2016-09-20 11:34:37 +01:00
+								{% extends "withnav_template.html" %}
 								{% from "components/table.html" import list_table, field, hidden_field_heading %}
 								{% from "components/api-key.html" import api_key %}
 								{% block page_title %}
 								  API integration – GOV.UK Notify
 								{% endblock %}
 								{% block maincolumn_content %}
-												Add a new pattern for sub-navigation

This is like the ‘pill’ pattern that we use for filtering lists of
notifications. However it is meant for navigating between discrete
things, not a filtered view of the same list.

This is why is has a gutter between each item, and no selected state.

Turns out we already had a pattern about this on the dashboard, so this
commit also changes the dashboard to use the same code.

											
										
										
											2016-09-20 11:46:56 +01:00
+								  <h1 class="heading-large bottom-gutter">
-												Add an index page for the API integration

This commit adds a placeholder page which, for now, just has links to
the API keys page and links to the clients.

There’s more stuff to come on this page, but this commit just does the
reorganising so that it’s easier to review.

											
										
										
											2016-09-20 11:34:37 +01:00
+								    API integration
 								  </h1>
-												Add a new pattern for sub-navigation

This is like the ‘pill’ pattern that we use for filtering lists of
notifications. However it is meant for navigating between discrete
things, not a filtered view of the same list.

This is why is has a gutter between each item, and no selected state.

Turns out we already had a pattern about this on the dashboard, so this
commit also changes the dashboard to use the same code.

											
										
										
											2016-09-20 11:46:56 +01:00
+								  <nav class="grid-row">
 								    <div class="column-half">
 								      <a class="pill-separate-item" href="{{ url_for('.api_keys', service_id=current_service.id) }}">API keys</a>
 								    </div>
 								    <div class="column-half">
 								      <a class="pill-separate-item" href="{{ url_for('.api_documentation', service_id=current_service.id) }}">Documentation</a>
 								    </div>
 								  </nav>
-												Add an index page for the API integration

This commit adds a placeholder page which, for now, just has links to
the API keys page and links to the clients.

There’s more stuff to come on this page, but this commit just does the
reorganising so that it’s easier to review.

											
										
										
											2016-09-20 11:34:37 +01:00
 								{% endblock %}