darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-03-11 13:52:30 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
203393de235631db0ce3c38dec85da170a634fba
notifications-admin/app/templates/views/edit-email-template.html

43 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 %}
Refactor sticky button into component
2019-01-14 13:34:23 +00:00
{% from "components/page-footer.html" import sticky_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 %}
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% from "components/form.html" import form_wrapper %}
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
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% call form_wrapper() %}
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 %}
Refactor sticky button into component
2019-01-14 13:34:23 +00:00
{{ sticky_page_footer(
'Save'
) }}
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" %}
Restrict DD guidance to teams who can use it Document download is in private beta, which means most teams using Notify can’t see or use it. We shouldn’t confuse people by showing them this guidance, especially while it’s API-only.
2018-09-03 16:21:42 +01:00
{% if current_service.has_permission('upload_document') %}
{% include "partials/templates/guidance-send-a-document.html" %}
{% endif %}
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
</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>
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% endcall %}
Created an initial page for editing templates [ci skip]
2015-12-09 10:52:09 +00:00
{% endblock %}
Reference in New Issue Copy Permalink