app/templates/views/manage-users/edit-user-email.html

{% extends "withnav_template.html" %}
{% from "components/page-header.html" import page_header %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/form.html" import form_wrapper %}
{% from "components/components/back-link/macro.njk" import usaBackLink %}

{% block per_page_title %}
  Change team member’s email address
{% endblock %}


{% block backLink %}
  {{ usaBackLink({ "href": url_for('main.edit_user_permissions', service_id=current_service.id, user_id=user.id) }) }}
{% endblock %}

{% block maincolumn_content %}

  {{ page_header('Change team member’s email address') }}

  <p id="user_name">This will change the email address for {{ user.name }}.</p>
  {% call form_wrapper() %}
    {{ form.email_address(param_extensions={"classes": ""}, error_message_with_html=True) }}
    {{ page_footer('Save') }}
  {% endcall %}

{% endblock %}
-												Content changes following consultation with content and design pros :)

											
										
										
											2019-02-20 17:34:58 +00:00
+								{% extends "withnav_template.html" %}
-												Add GOV.UK Design System style back links

The Design System has standardised on back links being at the top of the
page, decorated with a small text-coloured arrow.

I think this makes more sense than having them at the bottom, because it
suggests, in some way, being able to go back before commiting to any of
the forms on the page. Whereas the things at the bottom of the page
should be performing actions on what’s in the page.

The reason for making this change now is that it de-clutters the area
around the green buttons. This was presenting a design challenge where
multiple levels of interaction were happening in the same form. Moving
these back links to the top of the page should mean that, in these
complicated forms, there’s one fewer thing to compete for the user’s
attention.

I’ve componentised this into a `page_header` macro so that the change is
easier to roll out and maintain.

											
										
										
											2019-04-29 11:44:05 +01:00
+								{% from "components/page-header.html" import page_header %}
-												Add a get view and template that enable changing team members email

											
										
										
											2019-02-19 15:35:51 +00:00
+								{% from "components/page-footer.html" import page_footer %}
 								{% from "components/form.html" import form_wrapper %}
-												Committing before merge

											
										
										
											2023-08-30 11:07:38 -04:00
+								{% from "components/components/back-link/macro.njk" import usaBackLink %}
-												Add a get view and template that enable changing team members email

											
										
										
											2019-02-19 15:35:51 +00:00
 								{% block per_page_title %}
-												Content changes following consultation with content and design pros :)

											
										
										
											2019-02-20 17:34:58 +00:00
+								  Change team member’s email address
-												Add a get view and template that enable changing team members email

											
										
										
											2019-02-19 15:35:51 +00:00
+								{% endblock %}
-												Move back link outside of main where it was used in the page header

The page_header macro includes an optional back link. Since the
page_header is always used inside `<main>`, where the back link should
not be, this stops setting the back link in the page header and instead
sets it in the new `backLink` block.

											
										
										
											2021-07-30 18:23:12 +01:00
 								{% block backLink %}
-												Committing before merge

											
										
										
											2023-08-30 11:07:38 -04:00
+								  {{ usaBackLink({ "href": url_for('main.edit_user_permissions', service_id=current_service.id, user_id=user.id) }) }}
-												Move back link outside of main where it was used in the page header

The page_header macro includes an optional back link. Since the
page_header is always used inside `<main>`, where the back link should
not be, this stops setting the back link in the page header and instead
sets it in the new `backLink` block.

											
										
										
											2021-07-30 18:23:12 +01:00
+								{% endblock %}
-												Add a get view and template that enable changing team members email

											
										
										
											2019-02-19 15:35:51 +00:00
+								{% block maincolumn_content %}
-												Move back link outside of main where it was used in the page header

The page_header macro includes an optional back link. Since the
page_header is always used inside `<main>`, where the back link should
not be, this stops setting the back link in the page header and instead
sets it in the new `backLink` block.

											
										
										
											2021-07-30 18:23:12 +01:00
+								  {{ page_header('Change team member’s email address') }}
-												Add GOV.UK Design System style back links

The Design System has standardised on back links being at the top of the
page, decorated with a small text-coloured arrow.

I think this makes more sense than having them at the bottom, because it
suggests, in some way, being able to go back before commiting to any of
the forms on the page. Whereas the things at the bottom of the page
should be performing actions on what’s in the page.

The reason for making this change now is that it de-clutters the area
around the green buttons. This was presenting a design challenge where
multiple levels of interaction were happening in the same form. Moving
these back links to the top of the page should mean that, in these
complicated forms, there’s one fewer thing to compete for the user’s
attention.

I’ve componentised this into a `page_header` macro so that the change is
easier to roll out and maintain.

											
										
										
											2019-04-29 11:44:05 +01: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 id="user_name">This will change the email address for {{ user.name }}.</p>
-												Add GOV.UK Design System style back links

The Design System has standardised on back links being at the top of the
page, decorated with a small text-coloured arrow.

I think this makes more sense than having them at the bottom, because it
suggests, in some way, being able to go back before commiting to any of
the forms on the page. Whereas the things at the bottom of the page
should be performing actions on what’s in the page.

The reason for making this change now is that it de-clutters the area
around the green buttons. This was presenting a design challenge where
multiple levels of interaction were happening in the same form. Moving
these back links to the top of the page should mean that, in these
complicated forms, there’s one fewer thing to compete for the user’s
attention.

I’ve componentised this into a `page_header` macro so that the change is
easier to roll out and maintain.

											
										
										
											2019-04-29 11:44:05 +01:00
+								  {% call form_wrapper() %}
-												Working through the Platform Admin section

											
										
										
											2023-08-17 15:13:26 -04:00
+								    {{ form.email_address(param_extensions={"classes": ""}, error_message_with_html=True) }}
-												Add GOV.UK Design System style back links

The Design System has standardised on back links being at the top of the
page, decorated with a small text-coloured arrow.

I think this makes more sense than having them at the bottom, because it
suggests, in some way, being able to go back before commiting to any of
the forms on the page. Whereas the things at the bottom of the page
should be performing actions on what’s in the page.

The reason for making this change now is that it de-clutters the area
around the green buttons. This was presenting a design challenge where
multiple levels of interaction were happening in the same form. Moving
these back links to the top of the page should mean that, in these
complicated forms, there’s one fewer thing to compete for the user’s
attention.

I’ve componentised this into a `page_header` macro so that the change is
easier to roll out and maintain.

											
										
										
											2019-04-29 11:44:05 +01:00
+								    {{ page_footer('Save') }}
 								  {% endcall %}
-												Add a get view and template that enable changing team members email

											
										
										
											2019-02-19 15:35:51 +00:00
 								{% endblock %}