mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-07-10 03:14:58 -04:00
If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones.
19 lines
788 B
HTML
19 lines
788 B
HTML
<nav class="navigation">
|
|
<ul>
|
|
<li><a href="{{ url_for('.dashboard', service_id=123) }}">Dashboard</a></li>
|
|
</ul>
|
|
<ul>
|
|
<li><a href="{{ url_for('.sendsms', service_id=123) }}">Send text messages</a></li>
|
|
<li><a href="{{ url_for('.sendemail', service_id=123) }}">Send emails</a></li>
|
|
<li><a href="{{ url_for('.showjobs', service_id=123) }}">Activity</a></li>
|
|
<li><a href="{{ url_for('.manage_templates', service_id=123) }}">Templates</a></li>
|
|
</ul>
|
|
<ul>
|
|
<li><a href="{{ url_for('.apikeys', service_id=123) }}">API keys and documentation</a></li>
|
|
</ul>
|
|
<ul>
|
|
<li><a href="{{ url_for('.manageusers', service_id=123) }}">Manage users</a></li>
|
|
<li><a href="{{ url_for('.service_settings', service_id=123) }}">Service settings</a></li>
|
|
</ul>
|
|
</nav>
|