app/templates/views/edit-email-template.html

{% extends "withnav_template.html" %}
{% from "components/textbox.html" import textbox %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/radios.html" import radios %}

{% block service_page_title %}
  {{ heading_action }} email template
{% endblock %}

{% block maincolumn_content %}

    <h1 class="heading-large">
      {{ heading_action }} email template
    </h1>

    <form method="post">
      <div class="grid-row">
        <div class="column-five-sixths">
          {{ textbox(form.name, width='1-1', hint='Your recipients won’t see this', rows=10) }}
          {{ textbox(form.subject, width='1-1', highlight_tags=True, rows=2) }}
          {{ textbox(form.template_content, highlight_tags=True, width='1-1', rows=8) }}
          {% if current_user.platform_admin %}
             {{ radios(form.process_type) }}
          {% endif %}
          {{ page_footer(
            'Save'
          ) }}
        </div>
        <aside class="column-whole">
          {% include "partials/templates/guidance-formatting.html" %}
          {% include "partials/templates/guidance-personalisation.html" %}
          {% include "partials/templates/guidance-optional-content.html" %}
          {% include "partials/templates/guidance-links.html" %}
        </aside>
      </div>
    </form>

{% endblock %}
-												Added main nav to logged in pages

											
										
										
											2015-12-14 16:53:07 +00:00
+								{% extends "withnav_template.html" %}
-												Add routing and pages for managing templates

So that users can see what it the flow is like to:
- add new templates
- edit existing templates

											
										
										
											2015-12-20 00:00:01 +00:00
+								{% from "components/textbox.html" import textbox %}
-												Rename `submit_form` component to `page_footer`

Submit form was
- a confusing name in itself
- not descriptive, because it also has an optional ‘back’ link

This commit also puts this component in as many pages as possible, stripping
out any hard-coded buttons and links.

It replaces any usage of buttons for ‘back’, because these are links, not
buttons (ie they don’t change any data).

											
										
										
											2016-01-07 20:11:22 +00:00
+								{% from "components/page-footer.html" import page_footer %}
-												Change the selectField on the edit template form to a radio field.
It's more stylish

											
										
										
											2017-01-19 09:35:34 +00:00
+								{% from "components/radios.html" import radios %}
-												Created an initial page for editing templates [ci skip]
											
										
										
											2015-12-09 10:52:09 +00:00
-												Include service name in page `<title>`

In pages specific to a service (e.g. dashboard and sub pages) the title
needs to distinguish which service it applies to. This is mainly to give
context to screen reader users who could be managing multiple services.

Implementing this uses template inheritance:

`page_title` includes `per_page_title` includes `service_page_title`

‘GOV.UK Notify’ is inserted into every page title.

Pages that set `service_page_title` get the service name inserted too.

											
										
										
											2017-02-13 10:45:15 +00:00
+								{% block service_page_title %}
 								  {{ heading_action }} email template
-												Created an initial page for editing templates [ci skip]
											
										
										
											2015-12-09 10:52:09 +00:00
+								{% endblock %}
-												Added main nav to logged in pages

											
										
										
											2015-12-14 16:53:07 +00:00
+								{% block maincolumn_content %}
-												Fix innaccurate headings on add/edit template page

The same `.html` file is shared between adding a template and editing a
template.

The page heading needs to be contextual to the URL, either ‘add’ or ‘edit’.
Somewhere along the way this got lost; this commit reinstates it.

											
										
										
											2016-03-11 07:45:10 +00:00
+								    <h1 class="heading-large">
 								      {{ heading_action }} email template
 								    </h1>
-												Created an initial page for editing templates [ci skip]
											
										
										
											2015-12-09 10:52:09 +00:00
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								    <form method="post">
-												Add a hint about how to use placeholders

Since placeholders (almost) work now, it’s worth telling people what the syntax
is.

This commit also removes the ‘template type’ picker, since you can only create
SMS templates at the moment. This will be revisited when we start looking at how
you add an email template.

											
										
										
											2016-02-18 07:44:50 +00:00
+								      <div class="grid-row">
-												More tweaks to width of elements

- SMS message preview gets slightly wider so it lines up with a 4/8
  column
- Edit email box gets wider to match more closely the width of the
  previewed and delivered emails

											
										
										
											2017-04-10 10:28:27 +01:00
+								        <div class="column-five-sixths">
-												Make subject a textarea

In order for subject lines to have their fields highlighted they have to
be textboxes. This is because the highlighting script only works with
textboxes that don’t scroll, either horizontally, vertically, or be
keying through them.

											
										
										
											2016-04-14 14:04:41 +01:00
+								          {{ textbox(form.name, width='1-1', hint='Your recipients won’t see this', rows=10) }}
-												Give more guidance about what to put in templates

There are some common questions that keep coming up when users are
editing or creating templates. This commit adds a pattern for sections
of guidance which can be shown/hidden.

It then modifies the guidance as follows.

Change:

- guidance about placeholders; give an example about what to do and what
  not to do (because the mistake we keep seeing people make is putting
  the thing itself, not the name of the thing)

Add (pretty basic at the moment but a need for these has come out of
research):

- guidance about links
- guidance about message length for text messages

											
										
										
											2016-06-20 11:38:30 +01:00
+								          {{ textbox(form.subject, width='1-1', highlight_tags=True, rows=2) }}
-												Allow rows to be passed to textbox

HTML textboxes have a rows attribute, which controls their height,
unless their height is overridden by CSS.

											
										
										
											2016-04-14 14:00:49 +01:00
+								          {{ textbox(form.template_content, highlight_tags=True, width='1-1', rows=8) }}
-												dont use has_permissions to check for platform admins

platform_admin is a separate concept to permissions, so by removing the
checks for it from the current_user.has_permissions function, we can
simplify things greatly. We already record on the user whether they're
a platform admin anyway.

											
										
										
											2018-02-27 16:45:20 +00:00
+								          {% if current_user.platform_admin %}
-												Change the selectField on the edit template form to a radio field.
It's more stylish

											
										
										
											2017-01-19 09:35:34 +00:00
+								             {{ radios(form.process_type) }}
-												Add a selectField to edit and create templates that is only visible for platform admins that makes the template a `priority` template.
There is a check that the template can not be created as priority if the user is not a platform admin.
There is a check that the template can not change the `priority` unless they are a platform admin.

											
										
										
											2017-01-18 15:11:34 +00:00
+								          {% endif %}
-												Enhance the ‘how to do placeholders’ hint

This commit makes the ‘how to do placeholders’ box part of the tour,
with the same blue background.

It also adds some Javascript enhancement so that:
- it responds to the contents of the message template
- has a ‘show me’ link which inserts ‘Dear ((name))’ into the template
  contents textbox

We’ve found that this has helped people understnad what placeholders
are, and how to do them.

											
										
										
											2016-03-30 11:39:16 +01:00
+								          {{ page_footer(
-												Move delete link from edit to view template page

Users were having trouble finding the delete template link. It sort of
made sense having it on the edit page before we had the view template
page. But it doesn’t make sense now – having to choose to ‘edit’ the
template before you can delete is counterintuitive.

The single template page is where you go to choose an action to perform
on your template. Deleting is a good example of an action you can
perform on a template.

So this commit moves the delete link from the edit template page to the
view template page.

It also puts the confirm banner on same page as the delete link

The idea being that, in order to make a decision about whether to delete
the template, it’s useful to be able to see the template you’re
deleting. There’s no user need to edit the template before you delete
it.

											
										
										
											2017-04-18 13:01:58 +01:00
+								            'Save'
-												Enhance the ‘how to do placeholders’ hint

This commit makes the ‘how to do placeholders’ box part of the tour,
with the same blue background.

It also adds some Javascript enhancement so that:
- it responds to the contents of the message template
- has a ‘show me’ link which inserts ‘Dear ((name))’ into the template
  contents textbox

We’ve found that this has helped people understnad what placeholders
are, and how to do them.

											
										
										
											2016-03-30 11:39:16 +01:00
+								          ) }}
-												Add a hint about how to use placeholders

Since placeholders (almost) work now, it’s worth telling people what the syntax
is.

This commit also removes the ‘template type’ picker, since you can only create
SMS templates at the moment. This will be revisited when we start looking at how
you add an email template.

											
										
										
											2016-02-18 07:44:50 +00:00
+								        </div>
-												Move template guidance underneath

Two problems with having it on the side:
- some users didn’t see it at all
- there wasn’t space to have additional guidance about Markdown-style
  formatting

											
										
										
											2016-07-01 17:07:39 +01:00
+								        <aside class="column-whole">
-												Add Gwen’s initial guidance about formatting

This is based on some work Gwen did for Civil Service Digital. Let’s
get it in for now so that we have a starting point from which to
improve.

This specifically doesn’t reference ‘optional’ placeholders because I
don’t know how best to explain those yet.

											
										
										
											2016-07-14 16:52:53 +01:00
+								          {% include "partials/templates/guidance-formatting.html" %}
-												Give more guidance about what to put in templates

There are some common questions that keep coming up when users are
editing or creating templates. This commit adds a pattern for sections
of guidance which can be shown/hidden.

It then modifies the guidance as follows.

Change:

- guidance about placeholders; give an example about what to do and what
  not to do (because the mistake we keep seeing people make is putting
  the thing itself, not the name of the thing)

Add (pretty basic at the moment but a need for these has come out of
research):

- guidance about links
- guidance about message length for text messages

											
										
										
											2016-06-20 11:38:30 +01:00
+								          {% include "partials/templates/guidance-personalisation.html" %}
-												Include service name in page `<title>`

In pages specific to a service (e.g. dashboard and sub pages) the title
needs to distinguish which service it applies to. This is mainly to give
context to screen reader users who could be managing multiple services.

Implementing this uses template inheritance:

`page_title` includes `per_page_title` includes `service_page_title`

‘GOV.UK Notify’ is inserted into every page title.

Pages that set `service_page_title` get the service name inserted too.

											
										
										
											2017-02-13 10:45:15 +00:00
+								          {% include "partials/templates/guidance-optional-content.html" %}
-												Give more guidance about what to put in templates

There are some common questions that keep coming up when users are
editing or creating templates. This commit adds a pattern for sections
of guidance which can be shown/hidden.

It then modifies the guidance as follows.

Change:

- guidance about placeholders; give an example about what to do and what
  not to do (because the mistake we keep seeing people make is putting
  the thing itself, not the name of the thing)

Add (pretty basic at the moment but a need for these has come out of
research):

- guidance about links
- guidance about message length for text messages

											
										
										
											2016-06-20 11:38:30 +01:00
+								          {% include "partials/templates/guidance-links.html" %}
 								        </aside>
-												Add a hint about how to use placeholders

Since placeholders (almost) work now, it’s worth telling people what the syntax
is.

This commit also removes the ‘template type’ picker, since you can only create
SMS templates at the moment. This will be revisited when we start looking at how
you add an email template.

											
										
										
											2016-02-18 07:44:50 +00:00
+								      </div>
-												Replace tabs with two spaces for consistency

											
										
										
											2016-02-01 16:57:29 +00:00
+								    </form>
-												Created an initial page for editing templates [ci skip]
											
										
										
											2015-12-09 10:52:09 +00:00
 								{% endblock %}