mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-08-18 21:49:37 -04:00
74fb30ce5f
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.
31 lines
850 B
HTML
31 lines
850 B
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 %}
|
|
|
|
{% block per_page_title %}
|
|
Confirm change of mobile number
|
|
{% endblock %}
|
|
|
|
{% block maincolumn_content %}
|
|
|
|
{{ page_header(
|
|
'Confirm change of mobile number',
|
|
back_link=url_for('.edit_user_mobile_number', service_id=service_id, user_id=user.id)
|
|
) }}
|
|
|
|
<div class="grid-row">
|
|
<div class="column-whole">
|
|
{% call form_wrapper() %}
|
|
<p>New mobile number:</p>
|
|
<div class="panel panel-border-wide bottom-gutter">
|
|
<p>{{ new_mobile_number }}</p>
|
|
</div>
|
|
<p>We will send {{ user.name }} a text message to tell them about the change.</p>
|
|
{{ page_footer('Confirm') }}
|
|
{% endcall %}
|
|
</div>
|
|
</div>
|
|
|
|
{% endblock %}
|