Skip to content

Conversation

@kr8n3r
Copy link
Contributor

@kr8n3r kr8n3r commented Jan 27, 2026

What

Update the guidance on the ‘Add a new service’ screen.
Explicitly tell users that the service name is for us (Notify), and not for recipients.

Trello card

Changes include:

  • content updates
  • removal of conditionally displayed content examples
  • stylistic tweaks
  • updates to tests

Why

In order to encourage users to choose a good service name (one which doesn’t cause problems when they request to go live), we need to change the name-your-service guidance.

Visuals

Before

notify localhost_6012_add-service (4) notify localhost_6012_add-service (3) notify localhost_6012_add-service (5)

After

notify localhost_6012_add-service (1) notify localhost_6012_add-service notify localhost_6012_add-service (2)

@kr8n3r kr8n3r force-pushed the update-name-your-service-guidance branch from 7e536c1 to f04f9e0 Compare January 27, 2026 18:43
@kr8n3r kr8n3r changed the title WIP: Update "name your service" page Update "Add a service" page Jan 27, 2026
@kr8n3r kr8n3r marked this pull request as ready for review January 27, 2026 18:44
This updates content based on the content document
(see Trello ticket) and makes the following markup
changes:

- removes conditional content from bullet points
- adds h2 before `organisation_type` to bring
the section into prominence
- adds organisation_type form paramaters
so that we can control the display of the legend
(we want the form to have a legend, but as we
have a h2 before it, we don;t need it to be visual)
- adds a 'details' element with new content
'CreateNhsServiceForm' classes

- Update the service name field label
- Remove the form label from OrganisationTypeField
class as we now control the legend text in the
view.
Update tests that check for H1 text
Remove the test that was testing conditional
content in the bullet point examples, as
they're no loneger present.
@kr8n3r kr8n3r force-pushed the update-name-your-service-guidance branch from f04f9e0 to d94db40 Compare January 29, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants