Skip to content

AP-212 Make navigation consistent with the copy #423

Open
ZahuraB wants to merge 10 commits intomainfrom
AP_212_make_nav_consistent_with_body_copy
Open

AP-212 Make navigation consistent with the copy #423
ZahuraB wants to merge 10 commits intomainfrom
AP_212_make_nav_consistent_with_body_copy

Conversation

@ZahuraB
Copy link
Copy Markdown
Contributor

@ZahuraB ZahuraB commented Dec 4, 2025

https://govukverify.atlassian.net/browse/AP-212

Why

The left hand navigation is currently inconsistent with the copy in the main body of the content.

What

Update the copy and links to match the left hand navigation.

Technical writer support

Yes. @ImogenCraigmile to review.

How to review

See PR

Changelog

If this change is significant (for example, launching a new feature or deprecating a feature), you should update the changelog found at partials/_changelog.erb under the heading 'Documentation updates'.

Confirm

  • I have checked if any docs change here also requires updates to other repositories (ADRs / RFCs, README.md, Team Manual, elsewhere in these docs)
  • Where there is any overlap I have updated or opened a PR for corresponding changes

Copy link
Copy Markdown
Contributor

@ImogenCraigmile ImogenCraigmile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording all looks good to me. I can see that the checks are failing due to links that I don't think we've touched here. I might try and rerun it to fix these but good work Zahura

Copy link
Copy Markdown
Contributor

@ImogenCraigmile ImogenCraigmile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good to me on the wording side but aware that we still have the link issues. Just wanted to approve so that when @pauldougan has had a look it can get merged in the new year!

Copy link
Copy Markdown
Contributor

@pauldougan pauldougan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ZahuraB I made some suggestions for this PR, happy to discuss further


Before you can start integrating with GOV.UK One Login, you need to:

* [consider how to integrate third-party platforms with GOV.UK One Login][integrate.connect-third-party]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "consider how to integrate third-party platforms with GOV.UK One Login" is a much better description of what that page is for and we should apply this copy to the title of the page titled "Integrating third-party platforms with GOV.UK One Login" - i think we should make the page title and the copy consistent before-integrating/integrating-third-party-platform/

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we need consistency between the page and the navigation. In this case I feel that changing it to "consider how to integrate third-party platforms" would make the title too long. "Integrating-third-party-platform" front loads the information better which is easier for the reader to scan.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ZahuraB & @pauldougan - Maybe we can agree on a phrase that suits both locations. I suggest "Consider limitations when integrating with third-party platforms".

@ZahuraB ZahuraB requested a review from pauldougan February 26, 2026 14:43
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.

4 participants