Skip to content

CCM-25839 added last updated copy to pricing pages - #322

Merged
stacey-budd merged 1 commit into
mainfrom
page-last-updated
Nov 11, 2026
Merged

stacey-budd merged 1 commit into
mainfrom
page-last-updated

Conversation

@stacey-budd

Copy link
Copy Markdown
Contributor

Description

Added Last updated: [date] line to the top of the following pages:

https://notify.nhs.uk/pricing-and-commercial/
https://notify.nhs.uk/pricing-and-commercial/text-messages
https://notify.nhs.uk/pricing-and-commercial/letters

Context

Wayne Shirt highlighted a pricing discrepancy on the hompage of the NHS Notify website, where our text message pricing was out of date with previous changes to the https://notify.nhs.uk/pricing-and-commercial/text-messages page.

Following updates to the homepage, Wayne and Sommer Croft asked if we could add confirmation to our website pages of when content was last reviewed. The 'page updated' pattern has recently been introduced in the NHS service manual backlog, but it's not yet an official NHS design component: nhsuk/nhsuk-service-manual-community-backlog#310 (comment)

As an interim measure, the content designers agreed to add text to the top of the relevant /pricing-and-commercial/ pages, to confirm when the page was last updated.

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 a review from a team as a code owner November 11, 2026 16:25
@stacey-budd
stacey-budd merged commit d37d6f1 into main Nov 11, 2026
41 checks passed
@stacey-budd
stacey-budd deleted the page-last-updated branch November 11, 2026 16:37
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