darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-08-15 15:28:50 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
3563dcc010a5b92ec899cd43b48b8dfb4bf47463
notifications-admin/app/templates/views/dashboard/get-started.html

24 lines
781 B
HTML
Raw Normal View History

Put some statistics on the dashboard This commit adds two new sections to the dashboard 1. A banner telling you about trial mode, including a count of how many messages you have left today, which is a restriction of trial mode 2. Panels with counts of how many emails and text messages have been sent in a day, plus the failure rates for each It does **not**: - link through to any further information about what trial mode is (coming later) - link through to pages for the failure rates (coming later) - change the ‘recent jobs’ section to ‘recent notifications’
2016-03-17 11:45:48 +00:00
{% from "components/banner.html" import banner_wrapper %}
Make ‘get started’ work for emails and texts Previously the ‘get started’ block on the dashboard pushed users into starting with a text message. This led to users writing email content into a tet message template because it didn’t match their expectations. Also, the ‘send yourself a test’ link from the dashboard: - wasn’t much used, because users responded to the similar call to action on the choose template page instead - was confusing if you had created an email template because it presupposed that you’d created a text message template So this commit changes the ‘get started’ block to be a choice between creating an email template or a text message template. We reckon that the language of ‘set up’ will help establish that templates are not equivalent to individual messages. This language is now repeated on the ‘choose template’ page when you don’t have templates as well.
2016-04-01 07:32:02 +01:00
{% if current_user.has_permissions(['manage_templates']) %}
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119
2016-04-01 10:54:55 +01:00
{% call banner_wrapper(type='tour') %}
<h2 class="heading-large">You’re ready to get started</h2>
<p>
Added current_service to flask context and template context. Fix all tests and conflicts. Removed comment line.
2016-04-04 16:53:52 +01:00
<a href='{{ url_for(".add_service_template", service_id=current_service.id, template_type="sms") }}'>
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119
2016-04-01 10:54:55 +01:00
Set up a text message template
</a>
</p>
<p>
Added current_service to flask context and template context. Fix all tests and conflicts. Removed comment line.
2016-04-04 16:53:52 +01:00
<a href='{{ url_for(".add_service_template", service_id=current_service.id, template_type="email") }}'>
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119
2016-04-01 10:54:55 +01:00
Set up an email template
</a>
</p>
{% endcall %}
Make ‘get started’ work for emails and texts Previously the ‘get started’ block on the dashboard pushed users into starting with a text message. This led to users writing email content into a tet message template because it didn’t match their expectations. Also, the ‘send yourself a test’ link from the dashboard: - wasn’t much used, because users responded to the similar call to action on the choose template page instead - was confusing if you had created an email template because it presupposed that you’d created a text message template So this commit changes the ‘get started’ block to be a choice between creating an email template or a text message template. We reckon that the language of ‘set up’ will help establish that templates are not equivalent to individual messages. This language is now repeated on the ‘choose template’ page when you don’t have templates as well.
2016-04-01 07:32:02 +01:00
{% else %}
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119
2016-04-01 10:54:55 +01:00
{% call banner_wrapper(type='mode') %}
Make ‘get started’ work for emails and texts Previously the ‘get started’ block on the dashboard pushed users into starting with a text message. This led to users writing email content into a tet message template because it didn’t match their expectations. Also, the ‘send yourself a test’ link from the dashboard: - wasn’t much used, because users responded to the similar call to action on the choose template page instead - was confusing if you had created an email template because it presupposed that you’d created a text message template So this commit changes the ‘get started’ block to be a choice between creating an email template or a text message template. We reckon that the language of ‘set up’ will help establish that templates are not equivalent to individual messages. This language is now repeated on the ‘choose template’ page when you don’t have templates as well.
2016-04-01 07:32:02 +01:00
<p>
You need to ask your service manager to set up some templates before you can send messages
</p>
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119
2016-04-01 10:54:55 +01:00
{% endcall %}
Make ‘get started’ work for emails and texts Previously the ‘get started’ block on the dashboard pushed users into starting with a text message. This led to users writing email content into a tet message template because it didn’t match their expectations. Also, the ‘send yourself a test’ link from the dashboard: - wasn’t much used, because users responded to the similar call to action on the choose template page instead - was confusing if you had created an email template because it presupposed that you’d created a text message template So this commit changes the ‘get started’ block to be a choice between creating an email template or a text message template. We reckon that the language of ‘set up’ will help establish that templates are not equivalent to individual messages. This language is now repeated on the ‘choose template’ page when you don’t have templates as well.
2016-04-01 07:32:02 +01:00
{% endif %}
Reference in New Issue Copy Permalink