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

36 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" %}
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
Changing the govuk grid to USWDS
2023-08-23 16:18:25 -04:00
<div class="grid-row">
<div class="grid-col-8">
Updating site to use USWDS styles (#509) * Updated header and footer * Updated fonts * Moved files around and updated gulpfile to correct the build process when it goes to production * Adjusted grid templating * Added images to assets * Update app/templates/components/uk_components/footer/template.njk Co-authored-by: Steven Reilly <stvnrlly@users.noreply.github.com>
2023-06-06 15:28:24 -04:00
<h1 class="font-body-2xl margin-bottom-3">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) %}
Removing govuk utility classes
2023-08-25 11:38:07 -04:00
{{ form.name(param_extensions={}) }}
Convert EmailFields to GovukEmailFields Changes those fields (and sometimes also regular text input fields) in the following forms: - LoginForm - RegisterUserForm - ChangeEmailForm - FeedbackOrProblem - AcceptAgreementForm - ChangeNameForm (only name field here, but used in the same template field as ChangeEmailForm here: app/templates/views/user-profile/change.html) Also includes changes to templates that use this form and associated tests.
2020-08-07 15:16:04 +01:00
{{ form.email_address(
param_extensions={
a few more organisation edits
2023-01-05 21:33:15 -05:00
"hint": {"text": "Must be from a public sector organization"},
Convert EmailFields to GovukEmailFields Changes those fields (and sometimes also regular text input fields) in the following forms: - LoginForm - RegisterUserForm - ChangeEmailForm - FeedbackOrProblem - AcceptAgreementForm - ChangeNameForm (only name field here, but used in the same template field as ChangeEmailForm here: app/templates/views/user-profile/change.html) Also includes changes to templates that use this form and associated tests.
2020-08-07 15:16:04 +01:00
"autocomplete": "email"
},
error_message_with_html=True
) }}
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">
Update UKMobileNumber & InternationalPhoneNumber Changes those classes so they have the same interface as a GOVUK field when instantiated and render GovukTextInputField HTML. Includes changes to templates that use this form and associated tests.
2020-08-07 13:46:15 +01:00
{{ form.mobile_number(param_extensions={
"hint": {"text": "We’ll send you a security code by text message"},
}) }}
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>
Removing govuk utility classes
2023-08-25 11:38:07 -04:00
{{ form.password(param_extensions={"hint": {"text": "At least 8 characters"}, "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