Add a checklist to the request to go live page

[quis]

We reckon that by making this list respond to what the user has done that it will be more effective than a static list.

We don‘t want to block anyone from making the request. The request to go live is essentially the end of our conversion funnel. So introducing a roadblock feels like a dangerous thing to do. These changes represent more of a speedbump.

Check for team members

One of the things that we want to check before a service goes live is that they have at least two team members with the manage service permission. Anyone who can make a request to go live has this permission, so that means one additional user is needed. This is what we can automatically communicate to the user.

Check for templates

We need users to have created some templates before they go live, so we can see what kind of messages they intend to send. This won’t catch users who only have ‘testing’ template(s) set up, but it will at least warn those who have none.

Check for reply to email address

We require that a user has a real reply-to email address before going live. We can partially automate this by at least telling users who haven’t done this.

This only applies for users that have email templates; we shouldn’t bother users who aren’t going to send emails about this.

Before

After

---

Addresses alphagov/notify-design-archive#4