mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-08-14 23:08:07 -04:00
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.
65 lines
2.3 KiB
HTML
65 lines
2.3 KiB
HTML
{% extends "withnav_template.html" %}
|
||
{% from "components/api-key.html" import api_key %}
|
||
{% from "components/page-header.html" import page_header %}
|
||
{% from "components/page-footer.html" import page_footer %}
|
||
{% from "components/table.html" import row_group, row, text_field, edit_field, field, boolean_field, list_table with context %}
|
||
|
||
{% block service_page_title %}
|
||
Email reply-to addresses
|
||
{% endblock %}
|
||
|
||
{% block maincolumn_content %}
|
||
|
||
{{ page_header(
|
||
'Email reply-to addresses',
|
||
back_link=url_for('main.service_settings', service_id=current_service.id)
|
||
) }}
|
||
|
||
<div class="user-list">
|
||
{% if not current_service.email_reply_to_addresses %}
|
||
<div class="user-list-item">
|
||
<span class="hint">You haven’t added any email reply-to addresses yet</span>
|
||
</div>
|
||
{% endif %}
|
||
{% for item in current_service.email_reply_to_addresses %}
|
||
<div class="user-list-item">
|
||
<h3>
|
||
<span class="heading-small">{{ item.email_address }}</span> <span class="hint">
|
||
{%- if item.is_default -%}
|
||
(default)
|
||
{% endif %}
|
||
</span>
|
||
</h3>
|
||
{% if current_user.has_permissions('manage_service') %}
|
||
<a class="user-list-edit-link" href="{{ url_for('.service_edit_email_reply_to', service_id =current_service.id, reply_to_email_id = item.id) }}">Change</a>
|
||
{% endif %}
|
||
{% if current_service.count_email_reply_to_addresses > 1 %}
|
||
{{ api_key(item.id, thing="ID") }}
|
||
{% endif %}
|
||
</div>
|
||
{% endfor %}
|
||
</div>
|
||
<div class="grid-row">
|
||
<div class="column-whole">
|
||
{% if current_user.has_permissions('manage_service') %}
|
||
<div class="js-stick-at-bottom-when-scrolling">
|
||
<a href="{{ url_for('.service_add_email_reply_to', service_id=current_service.id) }}" class="button">Add email reply-to address</a>
|
||
</div>
|
||
{% endif %}
|
||
</div>
|
||
<div class="column-five-sixths">
|
||
<p>
|
||
You need to add at least one reply-to address so recipients can reply to your messages.
|
||
</p>
|
||
<p>
|
||
Emails with a reply-to address:
|
||
</p>
|
||
<ul class="list list-bullet">
|
||
<li>are less likely to be labelled as spam</li>
|
||
<li>appear more trustworthy</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
|
||
{% endblock %}
|