darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-07-14 18:30:15 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
4d0da6594de60fcf37dc7796279462e32072d7a1
notifications-admin/app/templates/views/dashboard/template-statistics.html

48 lines
1.8 KiB
HTML
Raw Normal View History

Give headline numbers a blue, not black background These numbers don’t look very clickable white-on-black. Blue is the colour of links, so lets see if they are more clickable in blue. The same clicking-a-big-number thing is also happening on the activity page, so this commit also changes the activity page to look the same.
2016-06-08 15:41:02 +01:00
{% from "components/big-number.html" import big_number %}
Add a message count component The logic to say ‘1 email sent’ vs ‘12 text messages sent’ is repeated all over the place. So this commit adds a component to put it in one place.
2016-05-13 09:58:07 +01:00
{% from "components/message-count-label.html" import message_count_label %}
Make template graphs look consistent with page The graphs of template usage feel a bit weird to me now. 1. They are counts of messages, but the numbers are very small not big like we do everywhere else (eg the counts on a job) 2. There’s a lot of blue, especially for something that you can’t click This commit makes the numbers bigger and the bar chart grey.
2016-06-07 16:35:03 +01:00
{% from "components/big-number.html" import big_number %}
Show template usage broken down by month This follows on from: - https://github.com/alphagov/notifications-admin/pull/1094 - https://github.com/alphagov/notifications-admin/pull/1109 It depends on: - [ ] https://github.com/alphagov/notifications-api/pull/829 A year is too long. Month-by-month is a better timeframe for making decisions or seeing patterns in your usage.
2017-02-16 15:08:16 +00:00
{% from "components/table.html" import list_table, field, right_aligned_field_heading, row_heading, spark_bar_field %}
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
{% from "components/show-more.html" import show_more %}
Add a page to show delivery rates week-by-week Implements https://github.com/alphagov/notifications-api/pull/286 Will always show weeks as Monday to Sunday.
2016-05-03 13:25:22 +01:00
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
<div class="ajax-block-container">
{% if template_statistics|length > 1 %}
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
<div class='template-statistics-table'>
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
{% call(item, row_number) list_table(
template_statistics,
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
caption="By template",
caption_visible=True,
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
empty_message='',
field_headings=[
'Template',
'Messages sent'
],
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
field_headings_visible=False
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
) %}
Add ids for dashboard numbers and stats to be used by the functional tests
2016-10-13 10:52:09 +01:00
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
{% call row_heading() %}
{% if item.is_precompiled_letter %}
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
<span class="template-statistics-table-template-name">
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
Provided as PDF
</span>
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
<span class="template-statistics-table-hint">
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
Letter
</span>
{% else %}
Update all links to use GOVUK Frontend style Includes: - turning off :visited styles to match existing design - swapping heading classes used to make links bold for the GOVUK Frontend bold override class - adding visually hidden text to some links to make them work when isolated from their context We may need to revisit whether some links, such as those for documentation and features, may benefit from having some indication that their target has been visited.
2019-12-06 07:53:46 +00:00
<a class="govuk-link govuk-link--no-visited-state template-statistics-table-template-name" href="{{ url_for('.view_template', service_id=current_service.id, template_id=item.template_id) }}">{{ item.template_name }}</a>
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
<span class="template-statistics-table-hint">
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
{{ message_count_label(1, item.template_type, suffix='template')|capitalize }}
</span>
{% endif %}
{% endcall %}
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
Remove unreachable code An `if` statement higher up the page means this code will never get run now. We can simplify the template by removing it.
2019-10-30 10:46:48 +00:00
{{ spark_bar_field(item.count, most_used_template_count, id=item.template_id) }}
Don’t right align template stats for one template We don’t show the graph if a user has only used one template.
2017-02-15 14:01:52 +00:00
{% endcall %}
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
{{ show_more(
url_for('.template_usage', service_id=current_service.id),
Revert "Revert "Restyle template statistics and received text messages""
2020-02-18 16:16:51 +00:00
'See templates used by month',
with_border=False
Don’t show template stats if one template used If you’ve only used one template then this section of the page isn’t doing its job, which is to show a comparison of the different kinds of message you’re showing. I think our initial assumption was that everyone would be using multiple templates, so it was good to show this part of the page during the onboarding, to show users where the information was going to appear. But we have lots of services who only send one template now, typically where they’re populating the contents of the template themselves. In which case this part of the page doesn’t offer them any value.
2019-10-25 15:52:22 +01:00
) }}
</div>
{% endif %}
Make template statistics on the dashboard a table It was a `<dl>` before which is kinda weird. Especially when the jobs table was a real `<table>`. It also means we can give it column headings so that new and invited users have a better idea of what it is.
2016-06-17 15:03:34 +01:00
</div>
Reference in New Issue Copy Permalink