darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-09-06 18:58:25 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
eb343e493745ea4f2ebd49974edcfc437b35fb99
notifications-admin/app/templates/views/broadcast/tour/4.html

36 lines
1.1 KiB
HTML
Raw Normal View History

Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
{% from "components/banner.html" import banner_wrapper %}
{% extends "admin_template.html" %}
{% block per_page_title %}
Reword title of screen 4 of broadcast tour We want to emphasise the difference over the similarity.
2020-08-27 11:31:06 +01:00
An alert is not a normal text message.
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
{% endblock %}
{% set mainClasses = "govuk-!-padding-top-0 govuk-!-padding-bottom-0" %}
{% block content %}
Improve pacing and sequence of information in the broadcast tour This commit refines which information we show on each page. Specifically we’re - adding some wording (‘at exactly the same time’) to try to communicate the immediacy - giving the ‘loud noises’ message it’s own screen to really draw attention to it - moving the ‘no phone numbers bit’ later in the journey, and experimenting with explaining why that is, to make it clearer how it’s different to a text message
2020-08-25 11:31:25 +01:00
<div class="banner-tour banner-tour-no-fixed-height govuk-!-margin-top-0">
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
<div class="govuk-grid-row">
Improve pacing and sequence of information in the broadcast tour This commit refines which information we show on each page. Specifically we’re - adding some wording (‘at exactly the same time’) to try to communicate the immediacy - giving the ‘loud noises’ message it’s own screen to really draw attention to it - moving the ‘no phone numbers bit’ later in the journey, and experimenting with explaining why that is, to make it clearer how it’s different to a text message
2020-08-25 11:31:25 +01:00
<div class="govuk-grid-column-one-half">
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
<h1 class="heading-medium">
Reword title of screen 4 of broadcast tour We want to emphasise the difference over the similarity.
2020-08-27 11:31:06 +01:00
An alert is not a normal text message.
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
</h1>
<p class="govuk-body heading-medium">
Improve pacing and sequence of information in the broadcast tour This commit refines which information we show on each page. Specifically we’re - adding some wording (‘at exactly the same time’) to try to communicate the immediacy - giving the ‘loud noises’ message it’s own screen to really draw attention to it - moving the ‘no phone numbers bit’ later in the journey, and experimenting with explaining why that is, to make it clearer how it’s different to a text message
2020-08-25 11:31:25 +01:00
It’s broadcast directly from a mobile phone mast, so you don’t
need to know anyone’s phone number.
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
</p>
<p class="govuk-body heading-medium">
Improve pacing and sequence of information in the broadcast tour This commit refines which information we show on each page. Specifically we’re - adding some wording (‘at exactly the same time’) to try to communicate the immediacy - giving the ‘loud noises’ message it’s own screen to really draw attention to it - moving the ‘no phone numbers bit’ later in the journey, and experimenting with explaining why that is, to make it clearer how it’s different to a text message
2020-08-25 11:31:25 +01:00
<a class="govuk-link govuk-link--no-visited-state" href='{{ url_for(".broadcast_tour", service_id=current_service.id, step_index=5) }}'>
Continue
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
</a>
</p>
</div>
Improve pacing and sequence of information in the broadcast tour This commit refines which information we show on each page. Specifically we’re - adding some wording (‘at exactly the same time’) to try to communicate the immediacy - giving the ‘loud noises’ message it’s own screen to really draw attention to it - moving the ‘no phone numbers bit’ later in the journey, and experimenting with explaining why that is, to make it clearer how it’s different to a text message
2020-08-25 11:31:25 +01:00
<div class="govuk-grid-column-one-half">
<img src="{{ asset_url('images/broadcast-tour/4.png') }}" alt="">
</div>
Refine broadcast tour based on research learnings We’ve shown the broadcast tour to a few users now. We’ve learned what concepts about broadcasting are and aren’t getting through. So what we’re emphasising here is: - the thing that appears on the phone (the ‘emergency alert’) not the technology (a ‘broadcast’) - how it’s different to other channels of messaging, eg text We’ve generally spent a lot more time on the content and illustrations this time around, so overall it’s should be clearer and shorter. This also expands the communication of training mode into the header, so it’s visible on every page (we can add another one for ‘live’ services later on).
2020-08-19 14:54:50 +01:00
</div>
</div>
{% endblock %}
Reference in New Issue Copy Permalink