app/templates/views/manage-templates.html

{% extends "withnav_template.html" %}
{% from "components/sms-message.html" import sms_message %}
{% from "components/email-message.html" import email_message %}
{% from "components/browse-list.html" import browse_list %}

{% block page_title %}
GOV.UK Notify | Manage templates
{% endblock %}

{% block maincolumn_content %}

    <div class="grid-row">
      <div class="column-two-thirds">

        <h1 class="heading-xlarge">Templates</h1>

        <p>
          <a href="{{ url_for('.add_service_template', service_id=service_id) }}">Create new template</a>

        {% for template in templates %}
          {% if template.get_field('template_type') == 'sms' %}
            {{ sms_message(
              template.get_field('content'),
              name=template.title,
              id=template.get_field('id'),
              edit_link=url_for('.edit_service_template', service_id=template.get_field('service'), template_id=template.get_field('id'))
            ) }}
          {% elif template.get_field('template_type') == 'email' %}
            {{ email_message(
              template.get_field('subject'),
              template.get_field('content'),
              name=template.get_field('name'),
              edit_link=url_for('.edit_service_template', service_id=template.get_field('service'), template_id=template.get_field('id'))
            ) }}
          {% endif %}
        {% endfor %}

      </div>
    </div>

{% endblock %}
Added main nav to logged in pages 2015-12-14 16:53:07 +00:00			`{% extends "withnav_template.html" %}`
Add some SMS messages to the choose template page 2016-01-13 16:21:29 +00:00			`{% from "components/sms-message.html" import sms_message %}`
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`{% from "components/email-message.html" import email_message %}`
			`{% from "components/browse-list.html" import browse_list %}`
Added initial template manage page [ci skip] 2015-12-09 10:47:38 +00:00
			`{% block page_title %}`
			`GOV.UK Notify \| Manage templates`
			`{% endblock %}`

Added main nav to logged in pages 2015-12-14 16:53:07 +00:00			`{% block maincolumn_content %}`

Add some SMS messages to the choose template page 2016-01-13 16:21:29 +00:00			`<div class="grid-row">`
			`<div class="column-two-thirds">`

Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`<h1 class="heading-xlarge">Templates</h1>`

Add link to delete a template This is a link not a button because: - it’s less prominent—delete is an infrequent action - it’s a two-step process, and only the second part changes any data (so it has a button) 2016-01-14 09:44:06 +00:00			`<p>`
Mapped template actions to the api and mocked tests. 2016-01-19 15:54:12 +00:00			`<a href="{{ url_for('.add_service_template', service_id=service_id) }}">Create new template</a>`
Add link to delete a template This is a link not a button because: - it’s less prominent—delete is an infrequent action - it’s a two-step process, and only the second part changes any data (so it has a button) 2016-01-14 09:44:06 +00:00
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`{% for template in templates %}`
Added fixes, displaying templates still needs to be fixed. 2016-01-22 11:14:56 +00:00			`{% if template.get_field('template_type') == 'sms' %}`
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`{{ sms_message(`
Fixed viewing templates. 2016-01-22 11:20:39 +00:00			`template.get_field('content'),`
			`name=template.title,`
Added template ID to template page, to allow users to identity required data for API calls. 2016-01-22 12:44:19 +00:00			`id=template.get_field('id'),`
Added fixes, displaying templates still needs to be fixed. 2016-01-22 11:14:56 +00:00			`edit_link=url_for('.edit_service_template', service_id=template.get_field('service'), template_id=template.get_field('id'))`
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`) }}`
Added fixes, displaying templates still needs to be fixed. 2016-01-22 11:14:56 +00:00			`{% elif template.get_field('template_type') == 'email' %}`
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`{{ email_message(`
Fixed viewing templates. 2016-01-22 11:20:39 +00:00			`template.get_field('subject'),`
			`template.get_field('content'),`
			`name=template.get_field('name'),`
Added fixes, displaying templates still needs to be fixed. 2016-01-22 11:14:56 +00:00			`edit_link=url_for('.edit_service_template', service_id=template.get_field('service'), template_id=template.get_field('id'))`
Add a prototype email template If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones. 2016-01-13 16:27:54 +00:00			`) }}`
			`{% endif %}`
Add some SMS messages to the choose template page 2016-01-13 16:21:29 +00:00			`{% endfor %}`

			`</div>`
			`</div>`
Added initial template manage page [ci skip] 2015-12-09 10:47:38 +00:00
			`{% endblock %}`