darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-09-06 12:48:25 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
07bcb4220e195cf970a980d56c17b1d00c7fb616
notifications-admin/app/templates/views/register.html

30 lines
1.1 KiB
HTML
Raw Normal View History

Make spacing and position of banners consistent Banners should always be the first thing on the page. Because headers already have padding we don’t want to put padding on the container. So banners should also have top padding to distance then from the red bar. They should also sit in the 3/4 column if the page has side navigation. This commit adds a new template (`withoutnav_template.html`) which extends `admin_template.html`. All views then extend one or the other, never the `admin_template.html` directly. This means that `admin_template.html` doesn’t have to make decisions about where the flash messages are displayed.
2016-02-01 12:15:38 +00:00
{% extends "withoutnav_template.html" %}
Add a WTForms-compatible textbox macro This macro: - accepts a WTForm form field as a parameter - renders a form field which follows the GOV.UK Elements patterns, both visually and in markup terms It then changes any page which uses either: - the old, non-WTForms macro or - the old, WTFforms `render_field` macro …to use this new macro and removes both of the old ones. It also adds the option to display hint text above the textbox.
2016-01-11 13:15:10 +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 %}
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 %}
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit.
2015-11-25 16:21:28 +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 per_page_title %}
Create an account
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit.
2015-11-25 16:21:28 +00:00
{% endblock %}
Make spacing and position of banners consistent Banners should always be the first thing on the page. Because headers already have padding we don’t want to put padding on the container. So banners should also have top padding to distance then from the red bar. They should also sit in the 3/4 column if the page has side navigation. This commit adds a new template (`withoutnav_template.html`) which extends `admin_template.html`. All views then extend one or the other, never the `admin_template.html` directly. This means that `admin_template.html` doesn’t have to make decisions about where the flash messages are displayed.
2016-02-01 12:15:38 +00:00
{% block maincolumn_content %}
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit.
2015-11-25 16:21:28 +00:00
Replace `grid-row` with `govuk-grid-row` Replaced all instances of `grid-row` in the HTML and JavaScript with `govuk-grid-row`, which is the new GOV.UK Frontend class.
2020-02-19 11:57:15 +00:00
<div class="govuk-grid-row">
Replace tabs with two spaces for consistency
2016-02-01 16:57:29 +00:00
<div class="column-two-thirds">
Make headings `.heading-large` instead of `.heading-xlarge`
2016-02-02 14:05:45 +00:00
<h1 class="heading-large">Create an account</h1>
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(autocomplete=True) %}
Make textboxes wider on create account
2016-02-04 12:40:56 +00:00
{{ textbox(form.name, width='3-4') }}
Add autocomplete to email address on register form GOV.UK Design System recommends: > You should also set the autocomplete attribute to email. This lets > browsers autofill the email address on a user’s behalf if they’ve > entered it previously. Only doing this on the register and sign in forms because it’s unlikely to be helpful where a user is trying to enter someone else’s email address.
2019-07-16 09:01:21 +01:00
{{ textbox(form.email_address, hint="Must be from a government organisation", width='3-4', safe_error_message=True, autocomplete='email') }}
Add some letter spacing to two factor textbox Entering, or reading back sequences of digits is easier when they’re a bit more spaced out. This is because we read words as shapes, but read numbers digit-by-digit. So this commit adjusts the tracking of the type to put a bit more space in for textboxes that are going to accept digits.
2017-10-16 16:51:44 +01:00
<div class="extra-tracking">
{{ textbox(form.mobile_number, width='3-4', hint='We’ll send you a security code by text message') }}
</div>
Replace all visually-hidden classes These have been replaced: https://design-system.service.gov.uk/get-started/updating-your-code/#helper-class-names
2019-10-21 15:18:25 +01:00
<input class="govuk-visually-hidden" aria-hidden="true" tabindex="-1" id="defeat-chrome-autocomplete">
Add autocomplete attribute to password fields This helps the browser autocomplete them with the right thing. Value based on https://www.w3.org/TR/WCAG21/#input-purposes
2019-07-16 17:01:54 +01:00
{{ textbox(form.password, hint="At least 8 characters", width='3-4', autocomplete='new-password') }}
make sure auth type is set when registering
2017-11-14 17:01:04 +00:00
{{form.auth_type}}
Replace tabs with two spaces for consistency
2016-02-01 16:57:29 +00:00
{{ page_footer("Continue") }}
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 %}
Replace tabs with two spaces for consistency
2016-02-01 16:57:29 +00:00
</div>
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit.
2015-11-25 16:21:28 +00:00
</div>
Updated html title [ci skip]
2015-12-01 09:53:14 +00:00
{% endblock %}
Reference in New Issue Copy Permalink