darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-08-11 09:28:27 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
077e90d4ffcd274f6470b24bc5f4fa83d2929d13
notifications-admin/app/templates/views/edit-email-template.html

40 lines
1.5 KiB
HTML
Raw Normal View History

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 %}
Created an initial page for editing templates [ci skip]
2015-12-09 10:52:09 +00:00
{% block page_title %}
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
{{ heading_action }} email template – GOV.UK Notify
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">
<div class="column-two-thirds">
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) }}
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>
<div class="column-two-thirds">
Move placeholder hint to align with subject If the hint aligns with the message body then it looks like you can only add placeholders to the body. This commit aligns it with the subject instead, and since it overlaps both it looks like you can add placeholders to both (hopefully).
2016-04-14 14:43:06 +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) }}
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(
'Save',
Fix template delete links. Fix bug with 'current_service' not available for non service urls. Code review adjustment. Static code check.
2016-04-13 16:19:34 +01:00
delete_link=url_for('.delete_service_template', service_id=current_service.id, template_id=template_id) if template_id or None,
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
delete_link_text='Delete this template'
) }}
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>
<div class="column-one-third">
Make the tour interactive _The code for this is quite hacky and light on tests. But I’d really like to get it in the app for the research tomorrow to see how well the feature works._ This commit changes the tour from being a set of static screens to some help which guides you through the process of sending your first test message. The theory behind this is that what users are really struggling with is the concept of a variable, rather than the relationship between the placeholders and the column headers. And like learning to program, the best way to learn is by taking an example and modifying it to your own needs. This means that when someone adds their first service we set them up an example email template and an example text message template. Then there is a guided, three step process where _all_ the user can do is send a test message to themselves. Once the message is sent, the user still has the example templates which they can edit, rather than having to remember what they’re supposed to be doing.
2016-05-20 12:05:05 +01:00
<label for='template_content' class='placeholder-hint banner-mode' data-textboxes-selector='#template_content,#subject' data-target-textbox-selector="#template_content">
Make the hint work for both subject and body This commit makes the placeholder hint not be dependent on their only being one textbox with placeholders on a page. To do this it needs to be its own module, because the two textboxes are each self-contained instances of the same module. The way I’ve gone about this is to make the placeholder hint accept a list of textboxes it should look in when deciding what message to display to the user. Most of the code is extracted from the existing placeholder highlighting module.
2016-04-14 14:38:36 +01:00
<div class="" id="placeholder-hint" aria-live="polite">
Make the tour interactive _The code for this is quite hacky and light on tests. But I’d really like to get it in the app for the research tomorrow to see how well the feature works._ This commit changes the tour from being a set of static screens to some help which guides you through the process of sending your first test message. The theory behind this is that what users are really struggling with is the concept of a variable, rather than the relationship between the placeholders and the column headers. And like learning to program, the best way to learn is by taking an example and modifying it to your own needs. This means that when someone adds their first service we set them up an example email template and an example text message template. Then there is a guided, three step process where _all_ the user can do is send a test message to themselves. Once the message is sent, the user still has the example templates which they can edit, rather than having to remember what they’re supposed to be doing.
2016-05-20 12:05:05 +01:00
<p>Anything in ((double brackets)) gets replaced when you send this message</p>
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
</div>
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
</label>
</div>
</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 %}
Reference in New Issue Copy Permalink