darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-02-24 04:10:57 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
203393de235631db0ce3c38dec85da170a634fba
notifications-admin/app/templates/views/support/index.html

44 lines
1.9 KiB
HTML
Raw Normal View History

Add a support index page Our support process is about to get more fully fledged so we’ll need an index page to route people properly. We reckon that users will also want to know what the support process is, so let’s explain it on this page.
2016-12-12 11:18:25 +00:00
{% extends "withoutnav_template.html" %}
Split support into two pages The kind of communications we’re getting at the moment can broadly be broken down into: - problems - questions and feedback We will need to triage problems differently, because they could potentially be urgent/severe/emergency/P1/whatever language we use. Questions or feedback will never be P1. Two reasons for making the user categorise their tickets themselves: - Outside of hours we can’t get someone out of bed in order to decide if a ticket is a problem or just feedback - We can tailor the subsequent pages to whether it’s a problem or feedback (eg showing a link to the status page if the user is having a problem) This commit let’s users make the choice with a pair of radio buttons. It also cleans up a bunch of the tests and parameterizes them so we’re testing the flow for both ticket types.
2016-12-12 11:25:43 +00:00
{% from "components/radios.html" import radios %}
Add a support index page Our support process is about to get more fully fledged so we’ll need an index page to route people properly. We reckon that users will also want to know what the support process is, so let’s explain it on this page.
2016-12-12 11:18:25 +00:00
{% from "components/page-footer.html" import page_footer %}
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% from "components/form.html" import form_wrapper %}
Add a support index page Our support process is about to get more fully fledged so we’ll need an index page to route people properly. We reckon that users will also want to know what the support process is, so let’s explain it on this page.
2016-12-12 11:18:25 +00:00
Include service name in page `<title>` In pages specific to a service (e.g. dashboard and sub pages) the title needs to distinguish which service it applies to. This is mainly to give context to screen reader users who could be managing multiple services. Implementing this uses template inheritance: `page_title` includes `per_page_title` includes `service_page_title` ‘GOV.UK Notify’ is inserted into every page title. Pages that set `service_page_title` get the service name inserted too.
2017-02-13 10:45:15 +00:00
{% block per_page_title %}
Support
Add a support index page Our support process is about to get more fully fledged so we’ll need an index page to route people properly. We reckon that users will also want to know what the support process is, so let’s explain it on this page.
2016-12-12 11:18:25 +00:00
{% endblock %}
{% block maincolumn_content %}
Updated support views to represent new url structure
2017-11-28 12:00:12 +00:00
<div class="grid-row">
<div class="column-two-thirds">
<h1 class="heading-large">Support</h1>
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% call form_wrapper(class="bottom-gutter-2") %}
Updated support views to represent new url structure
2017-11-28 12:00:12 +00:00
{{ radios(form.support_type) }}
{{ page_footer('Continue') }}
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better
2018-09-19 12:39:36 +01:00
{% endcall %}
Updated support views to represent new url structure
2017-11-28 12:00:12 +00:00
<p>If something’s wrong, you can <a href="https://status.notifications.service.gov.uk/"> check the GOV.UK Notify system status page</a> to see if we’re already aware of it.</p>
<h2 class="heading-medium">24-hour support</h2>
<p>You can get 24-hour online support for Notify if you have a live account.</p>
<h3 class="heading-small">During office hours</h3>
<p>Our office hours are 9.30am to 5.30pm, Monday to Friday.</p>
<p>Contact us using one of the options on this page and you’ll get a reply within 30 minutes.</p>
<p>You can also <a href="https://ukgovernmentdigital.slack.com/messages/govuk-notify">get in touch with us on Slack.</a></p>
<h3 class="heading-small">Out-of-hours</h3>
<p>Outside office hours, response times depend on whether you’re reporting an emergency or not.</p>
<p>If it’s an emergency, we’ll reply within 30 minutes and update you every hour until the problem’s fixed.</p>
<p>A problem is only classed as an emergency if:</p>
<ul class="list list-bullet">
<li>nobody on your team can sign in</li>
<li>a ‘technical difficulties’ error appears when you try to upload a file</li>
<li>a 500 response code appears when you try to send messages using the API</li>
</ul>
<p>We’ll reply during the next working day for any other problems.</p>
</div>
</div>
Add a support index page Our support process is about to get more fully fledged so we’ll need an index page to route people properly. We reckon that users will also want to know what the support process is, so let’s explain it on this page.
2016-12-12 11:18:25 +00:00
{% endblock %}
Reference in New Issue Copy Permalink