Skip to content

CCM-16060 Personalisation mini hub - #269

Open
stacey-budd wants to merge 3 commits into
mainfrom
CCM-16060-personalisation-updates
Open

CCM-16060 Personalisation mini hub#269
stacey-budd wants to merge 3 commits into
mainfrom
CCM-16060-personalisation-updates

Conversation

@stacey-budd

Copy link
Copy Markdown
Contributor

Description

Review of /personalisation/ website content and transformation into new mini hub pages, consisting of:

  • an overview of how personalisation works for message templates built using NHS Notify
  • a page explaining how to use Personal Demographics Service (PDS) data
  • a page explaining how to use custom data, including fields that aren't compatible with NHS Notify message templates
  • a page explaining how to provide custom data via an API or MESH request

The section on Example data has been removed, as this process no longer accurately affects the way message templates are proofed.

The /using-nhs-notify/personalisation page that's currently live has also been redirected to the new mini hub /personalising-your-messages/overview.

Context

The /using-nhs-notify/personalisation page was identified as a good fit for the modular mini hub layout during a content audit of the NHS Notify website.

User research findings from Using NHS Notify information architecture tree testing also provided valuable insight into user mental models and natural language models.

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.

@stacey-budd
stacey-budd requested review from a team as code owners August 13, 2026 13:57
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.

1 participant