app/templates/views/forgot-password.html

{% extends "base.html" %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/form.html" import form_wrapper %}

{% block per_page_title %}
  Forgot your password?
{% endblock %}

{% block maincolumn_content %}

<div class="grid-row">
  <div class="grid-col-8">
    <h1 class="font-body-2xl margin-bottom-3">Forgot your password?</h1>

    <p>We’ll send you an email to create a new password.</p>

    {% call form_wrapper() %}
      {{ form.email_address(error_message_with_html=True) }}
      {{ page_footer("Send email") }}
    {% endcall %}

  </div>
</div>

{% endblock %}
-												replaced content_tempalte and withoutnav_template with base.html

											
										
										
											2024-04-24 12:31:00 -07:00
+								{% extends "base.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/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 %}
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +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 %}
-												Addressing most of the low-lift items from the Notify content audit  (#491)


											
										
										
											2023-05-08 10:49:30 -04:00
+								  Forgot your password?
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +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 %}
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +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">Forgot your password?</h1>
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +00:00
-												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
+								    <p>We’ll send you an email to create a new password.</p>
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +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() %}
-												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(error_message_with_html=True) }}
-												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
+								      {{ page_footer("Send email") }}
-												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 %}
-												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
-												Added forgot password / create new password screens

Create new password would be sent in an email to the user.

											
										
										
											2015-11-30 16:19:59 +00:00
+								  </div>
 								</div>
-												Use a Node-based tools for handling assets

…or how to move a bunch of things from a bunch of different places into
`app/static`.

There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
  and meant depending on Ruby, and having the SASS Gem globally installed—so
  you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
  ironed out the initial rough patches

The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
  GOV.UK template as a proper dependency

…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.

Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).

											
										
										
											2015-12-15 08:20:25 +00:00
+								{% endblock %}