Commit Graph

3019 Commits

Author SHA1 Message Date
Chris Hill-Scott
8b9cc5f4dc Merge pull request #3134 from alphagov/relative-dates-jobs
Use relative dates for jobs on dashboard
2019-10-02 16:19:44 +01:00
Chris Hill-Scott
48940f7705 Merge pull request #3128 from alphagov/increase-letter-prices
Increase letter prices
2019-10-01 08:53:10 +01:00
Chris Hill-Scott
79369c38c7 Use relative dates for jobs on dashboard
For scheduled files we say ‘sending today at 5:00pm’ or ‘sending
tomorrow at 11:00am’. But once we’ve started processing these files we
say ‘Sent 27 September at 5:00pm’. This makes it sound like 27 September
is not today.

This commit makes the dates shown on the dashboard consistent, by saying
‘today’ and ‘yesterday’ instead of absolute dates.
2019-09-27 13:20:13 +01:00
Pete Herlihy
bdb4bceb57 Adding statement about compliance with NCSC Cloud Security Principles 2019-09-26 15:42:08 +01:00
Rebecca Law
d902ac3b44 Added the url for api docs.
Updated error message when js tests fail
2019-09-25 15:47:35 +01:00
karlchillmaid
7bdcf7414d Add 'link opens in new tab' explanation 2019-09-23 17:05:02 +01:00
karlchillmaid
fce4a36636 Update content 2019-09-23 17:01:59 +01:00
Chris Hill-Scott
767c7db48a Update app/templates/views/notifications/invalid_precompiled_letter.html 2019-09-23 13:22:29 +01:00
karlchillmaid
67647372f6 Update app/templates/views/service-settings/email-reply-to/_verify-updates.html
Prefer this option

Co-Authored-By: Chris Hill-Scott <me@quis.cc>
2019-09-23 13:22:29 +01:00
karlchillmaid
507d8542b8 Change could not to cannot 2019-09-23 13:22:29 +01:00
karlchillmaid
ab3bdaaa4d Change 'was not' to 'could not be'
Change 'was not' to 'could not be' – makes it sound more like there's a problem with the email address, and not a problem with the service.
2019-09-23 13:22:29 +01:00
karlchillmaid
89a609fb73 Replace haven't with have not 2019-09-23 13:22:28 +01:00
karlchillmaid
644686c3ce Replace haven't with have not 2019-09-23 13:22:27 +01:00
karlchillmaid
601078e06f Replace haven't with have not 2019-09-23 13:22:27 +01:00
karlchillmaid
bb1ad89357 Replace haven't with have not 2019-09-23 13:22:27 +01:00
karlchillmaid
c64f298820 Replace haven't with have not 2019-09-23 13:22:27 +01:00
karlchillmaid
0b0a303262 Replace haven't with have not 2019-09-23 13:22:27 +01:00
karlchillmaid
a8021fb965 Replace haven't with have not 2019-09-23 13:22:26 +01:00
karlchillmaid
f3dd497700 Replace haven't with have not 2019-09-23 13:22:26 +01:00
karlchillmaid
b7e9eb3d48 Replace hasn't with has not 2019-09-23 13:22:26 +01:00
karlchillmaid
03d70f5439 Replace aren't with are not 2019-09-23 13:22:26 +01:00
karlchillmaid
2387fcc8f1 Replace they've with they have 2019-09-23 13:22:17 +01:00
karlchillmaid
b27fd30d45 Replace wasn't with was not 2019-09-23 13:22:16 +01:00
karlchillmaid
90b8af63d5 Replace isn't with is not 2019-09-23 13:22:00 +01:00
karlchillmaid
73ce6eef83 Replace won't with will not 2019-09-23 13:22:00 +01:00
karlchillmaid
4c6f32df73 Replace won't with will not 2019-09-23 13:21:59 +01:00
karlchillmaid
2b0462f44f Replace won't with will not 2019-09-23 13:21:59 +01:00
karlchillmaid
5fea8739cd Replace won't with will not 2019-09-23 13:21:59 +01:00
karlchillmaid
c62f4ed706 Replace won't with will not 2019-09-23 13:21:59 +01:00
karlchillmaid
8811903040 Replace won't with will not 2019-09-23 13:21:59 +01:00
karlchillmaid
89ecee5d6f Replace don't with do not 2019-09-23 13:21:58 +01:00
karlchillmaid
6163b6f65f Replace don't with do not 2019-09-23 13:21:58 +01:00
karlchillmaid
fc4eb24795 Replace don't with do not 2019-09-23 13:21:58 +01:00
karlchillmaid
4f7d618d89 Update content to remove negative contraction 2019-09-23 13:21:58 +01:00
karlchillmaid
c96e29e1e8 Replace don't with do not 2019-09-23 13:21:58 +01:00
karlchillmaid
cc9bb476e5 Replace don't with do not 2019-09-23 13:21:57 +01:00
karlchillmaid
42663947fa Replace can't with cannot 2019-09-23 13:21:07 +01:00
karlchillmaid
fdb3ecc7d3 Replace can't with cannot 2019-09-23 13:21:07 +01:00
karlchillmaid
123d12bcdd Replace can't with cannot 2019-09-23 13:21:07 +01:00
karlchillmaid
4b23729ff6 Replace can't with cannot 2019-09-23 13:20:25 +01:00
karlchillmaid
0ff57d8514 Replace can't with cannot 2019-09-23 13:20:25 +01:00
karlchillmaid
92d3b99c7e Replace can't with cannot 2019-09-23 13:20:25 +01:00
karlchillmaid
3d36a99518 Replace can't with cannot 2019-09-23 13:20:24 +01:00
karlchillmaid
ce9d509601 Replace can't with cannot 2019-09-23 13:20:24 +01:00
Chris Hill-Scott
68c9147fec Merge pull request #3119 from alphagov/retire-old-static-content
Retire old static content pages
2019-09-23 13:19:01 +01:00
karlchillmaid
96a374044a Increase letter prices 2019-09-23 08:20:05 +01:00
Chris Hill-Scott
077dc194c6 Tell people to change their branding
In some cases it’s not appropriate for teams to have GOV.UK branding.
But they all start with it by default, if we can’t make a better guess.
We should be more explicit about this to reduce the number of teams
sending emails with the wrong branding.
2019-09-16 11:21:28 +01:00
Chris Hill-Scott
59ab064185 Play back current branding
We get a few tickets at the moment where people are asking for the
branding they already have.

We think that playing back the name of the branding on this page should
reduce how often that happens.
2019-09-16 11:20:23 +01:00
Chris Hill-Scott
afcdedf598 Allow elaboration when ‘something else’ is chosen
Letting people input a bit of free text should reduce the amount of back
and forth we have to do over support tickets when setting up someone’s
branding.

If something else is the only option then we don’t show the radio button
at all and have just the free text input on the page (not behind a
progressive disclosure).
2019-09-16 11:18:22 +01:00
Chris Hill-Scott
6d0d10e8de Only show relevant choices of email branding
Users who work in local government can’t have GOV.UK branding on their
emails. And only those working for Companies House (for example) can
request the Companies House branding.

This commit adds:
- new choices of email branding, which offer the name of the branding,
  rather than the style
- logic to filter this list to only the applicable options, based on
  what we know about the user, service and organisation

This is a change from the previous approach which put the onus on users
to figure out the style of branding they wanted, when we might already
know that a lot of the options weren’t available to them, or would be
inconsistent with the branding of other services in their organisation.
2019-09-16 11:03:52 +01:00