darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-06-04 05:20:46 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
403e133b80bb46292ea141efcb2f3bd39f3b70a1
notifications-admin/app/templates/views/edit-email-template.html

39 lines
1.4 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">
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
<div class="column-three-quarters">
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) }}
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>
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
<div class="column-three-quarters">
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>
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" %}
Added optional content guidance to email template view
2016-11-11 11:43:56 +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 %}
Reference in New Issue Copy Permalink