darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-08-14 02:48:45 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'feature/sidenav-expand-sublinks' of https://github.com/GSA/notifications-admin into feature/sidenav-expand-sublinks

Browse Source
This commit is contained in:
Jonathan Bobel
2025-01-14 09:55:56 -05:00
parent 872dbfd59a d5f4301747
commit ab911ce942
9 changed files with 4 additions and 115 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
app/main/views/index.py
View File

@@ -309,14 +309,12 @@ def studio():
# --- Redirects --- #
@main.route("/roadmap", endpoint="old_roadmap")
@main.route("/information-security", endpoint="information_security")
@main.route("/using_notify", endpoint="old_using_notify")
@main.route("/information-risk-management", endpoint="information_risk_management")
@main.route("/integration_testing", endpoint="old_integration_testing")
def old_page_redirects():
redirects = {
"main.old_roadmap": "main.roadmap",
"main.information_security": "main.using_notify",
"main.old_using_notify": "main.using_notify",
"main.information_risk_management": "main.security",

7
app/navigation.py
View File

@@ -40,12 +40,6 @@ class HeaderNavigation(Navigation):
"support": {
"support",
},
"features": {
"features",
"features_sms",
"roadmap",
"security",
},
"best_practices": {
"best_practices",
"clear_goals",
@@ -57,7 +51,6 @@ class HeaderNavigation(Navigation):
},
"using_notify": {
"get_started",
"using_notify",
"pricing",
"trial_mode_new",
"message_status",

6
app/templates/views/guidance/index.html
View File

@@ -15,19 +15,14 @@ your recipient to manage their benefits and increase follow-through.</p>
<p>Below we explain how to:</p>
<ul class="list list-bullet">
<li><a class="usa-link" href="#format-content">Format your content</a></li>
<li><a class="usa-link" href="#add-links">Add links</a></li>
<li><a class="usa-link" href="#personalize-content">Personalize your content</a></li>
<li><a class="usa-link" href="#conditional-content">Add conditional content</a></li>
<li><a class="usa-link" href="#indentify-program">Identify your program</a></li>
<li><a class="usa-link" href="#prepare-data">Prepare your data</a></li>
<li><a class="usa-link" href="#prevent-fraud">Prevent fraud</a></li>
</ul>
{# Format content #}
<h2 class="padding-top-1" id="format-content">Format your content</h2>
<p>Effective texts will help your message recipients take the steps needed to secure and keep the benefits and services
they depend on. To craft an effective text:</p>
<ul class="list list-bullet">
<li>Choose your messages thoughtfully. Text messages are best to remind/nudge someone to take a specific action or
@@ -45,7 +40,6 @@ they depend on. To craft an effective text:</p>
</ol>
{# Add links #}
<h2 class="padding-top-1" id="add-links">Add links</h2>
<p>When composing a text message, links to websites or online applications can help your recipient respond quickly.</p>
<ul class="list list-bullet">

2
app/templates/views/guides/clear-goals.html
View File

@@ -162,7 +162,7 @@
</div>
<p>
Review your drafted hypothesis with your team to make sure everyone is aligned on your desired goals. A clear and
concise hypothesis can help you decide how to <a href="../guides/write-for-action">write text message
concise hypothesis can help you decide how to <a href="../best-practices/write-for-action">write text message
content
that provokes action</a>.
</p>

4
app/templates/views/guides/rules-and-regulations.html
View File

@@ -22,7 +22,7 @@
If you do need expressed consent, consider including a pre-checked plain language opt-in (i.e. “It’s OK to text
me.”) on
digital forms. Be sure to ask for an up-to-date phone number and include a question about the recipient’s preferred
language for text messages if you expect to <a href="../guides/multiple-languages">translate your text
language for text messages if you expect to <a href="../best-practices/multiple-languages">translate your text
messages</a> in
languages other than English.
</p>
@@ -81,7 +81,7 @@
<h3>Opting out</h3>
<p>
There is no policy requirement for senders to communicate opt-out options, but <a
href="../guides/establish-trust#as-people-receive-texts"> including instructions in introductory and/or
href="../best-practices/establish-trust#as-people-receive-texts"> including instructions in introductory and/or
auto-response texts </a> on how to opt out and opt back in are effective ways to establish trust with your
audience.
</p>

2
app/templates/views/message-status.html
View File

@@ -77,7 +77,7 @@
<p>Sometimes Notify receives more detailed information from the carriers on the status of messages, and these can be found
in the downloadable reports. Not all carriers provide the same level of detail regarding delivery and some delivery
statutes have a slight variation in word choice. Notify includes this information in the reports to provide you as much
detail as possible. Remember, for <a class="usa-link" href="/features/security">security</a> purposes, detailed information is only available for seven days after a
detail as possible. Remember, for security purposes, detailed information is only available for seven days after a
message has been sent.</p>
<h2 class="heading-medium">Opting out</h2>

87
app/templates/views/roadmap.html
View File

@@ -1,87 +0,0 @@
{% extends "base.html" %}
{% from "components/table.html" import mapping_table, row, text_field, edit_field, field with context %}
{% from "components/content-metadata.html" import content_metadata %}
{% block per_page_title %}
Roadmap
{% endblock %}
{% block content_column_content %}
<h1 class="font-body-2xl margin-bottom-3">Roadmap</h1>
<!-- {{ content_metadata(
data={
"Last updated": "1 November 2022",
"Next review due on": "15 December 2022"
}
) }} -->
<p>The Notify roadmap shows what we’re working on and what we're planning to do next.</p>
<p>This roadmap is only a guide. It does not cover everything we do, and some things may change.</p>
<p>You can <a class="usa-link" href="{{url_for('.support')}}">contact us</a> if you have any questions about the roadmap or suggestions for new features.</p>
<h2 id="things-we-are-working-on">What we’re working on</h2>
<h3 id="now">Now</h3>
<p>We are investigating the Notify concept, building on the notifications tool pioneered by the UK.</p>
<p>To do this, we are convening a pilot with a small set of partners.</p>
<p>Goals during this stage:</p>
<ul class="list list-bullet">
<li>Achieve compliance to begin piloting, such as ATO and privacy standards.
<svg class="usa-icon" aria-hidden="true" focusable="false" role="img">
<use xlink:href="/assets/img/sprite.svg#check"></use>
</svg>
</li>
<li>Demonstrate that a government-run notifications tool provides a unique value.</li>
<li>Gather data from the pilot to improve the product.</li>
</ul>
<p>Features prioritized during this stage:</p>
<ul class="list list-bullet">
<li>Bulk, individually customizable one-way SMS sending via web UI</li>
<li>Organization permissions settings for various team members to edit/send</li>
<li>Reusable message templates</li>
<li>Seven-day records deletion</li>
<li>Message send/failure analytics</li>
</ul>
<h3 id="next">Next</h3>
<p>If the pilot is successful, we hope to recruit additional partners to improve outcomes for low-income individuals and families.</p>
<p>Goals during this stage:</p>
<ul class="list list-bullet">
<li>Complement Notify with practical guidance and support services.</li>
<li>Iterate on existing features and implement new features based on what we've learned so far.</li>
<li>Hone our measurement approaches to better quantify impact.</li>
</ul>
<p>Features prioritized during this stage:</p>
<ul class="list">
<li>SMS sending via API integration</li>
<li>Self-service account creation</li>
<li>Application status page</li>
<li>Improved scheduled send option</li>
</ul>
<h3 id="later">Later</h3>
<p>In the future, we may decide to expand beyond SMS, or to offer the service government-wide.</p>
<p>Features to be considered during this stage:</p>
<ul class="list">
<li>Two-way messaging</li>
<li>Multilingual interface and content library options</li>
<li>Recurring scheduled send (such as “Send each Monday for 3 weeks”)</li>
</ul>
{% endblock %}

4
tests/app/main/views/test_index.py
View File

@@ -176,10 +176,6 @@ def test_old_static_pages_redirect(client_request, view, expected_view, mocker):
)
def test_old_using_notify_page(client_request):
client_request.get("main.using_notify", _expected_status=410)
def test_css_is_served_from_correct_path(client_request):
page = client_request.get("main.documentation") # easy static page

5
tests/app/test_navigation.py
View File

@@ -95,7 +95,6 @@ EXCLUDED_ENDPOINTS = tuple(
"error",
"establish_trust",
"features",
"features_sms",
"find_services_by_name",
"find_users_by_email",
"forgot_password",
@@ -140,7 +139,6 @@ EXCLUDED_ENDPOINTS = tuple(
"notifications_sent_by_service",
"old_guest_list",
"old_integration_testing",
"old_roadmap",
"old_service_dashboard",
"old_using_notify",
"organization_billing",
@@ -169,9 +167,7 @@ EXCLUDED_ENDPOINTS = tuple(
"resume_service",
"revalidate_email_sent",
"revoke_api_key",
"roadmap",
"rules_and_regulations",
"security",
"security_policy",
"send_files_by_email",
"send_files_by_email_contact_details",
@@ -247,7 +243,6 @@ EXCLUDED_ENDPOINTS = tuple(
"user_profile_name",
"user_profile_password",
"user_profile_preferred_timezone",
"using_notify",
"verify",
"verify_email",
"view_job",