Skip to content

Conversation

@jakecosgrove
Copy link
Contributor

Description

This PR includes:

  • 3 new pages in /using-nhs-notify for each user segment (/campaigns, event based messaging and direct messaging)
  • new includes for the expander component (but not yet included in live site as icons do not appear)
  • new custom-components folder inside /includes for custom table created for user segment pages - these have been dubbed 'feature lists'
  • missing page links on /using-nhs-notify sub navigation (/message-status and /approve-your-messages)

Context

This PR includes the first version of the 'out of the box' offering of NHS Notify.

It is part of a strategic product decision to package specific solutions or configurations of NHS Notify that correspond with a prospects specific use case. Creating packaged solutions of NHS Notify is part of an initiative to reduce the time it takes to convert a prospect into an integrator.

The hypothesis is that:

If we provide a solution of NHS Notify that corresponds with a segmentation of user...
We should see that prospects can identify that the solution meets the needs of their use case and decide to integrate with NHS Notify on the basis of that solution. This should then make onboarding that prospect quicker and easier as their requirements should already be captured by the solution.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@jakecosgrove jakecosgrove requested a review from a team as a code owner May 22, 2025 21:52
@jakecosgrove jakecosgrove merged commit 461feb5 into main May 23, 2025
17 of 19 checks passed
@jakecosgrove jakecosgrove deleted the out-of-box-v1 branch May 23, 2025 13:03
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