Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-route archived link on "Getting started: production" page #3407

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dav-idc
Copy link
Contributor

@dav-idc dav-idc commented Jan 5, 2024

It looks like the old link here was archived in November / December, as part of the 5.0 release. I feel like routing people to the Frontend docs page on making sure to keep up to date with the latest version is a pretty valuable alternative piece of guidance for teams still stuck on GOV.UK Elements, Templates, etc.

It looks like the old link here was archived in November / December, as part of the 5.0 release. I feel like routing people to the Frontend docs page on making sure to keep up to date with the latest version is a pretty valuable alternative piece of guidance for teams still stuck on GOV.UK Elements, Templates, etc.
Copy link

netlify bot commented Jan 5, 2024

You can preview this change here:

Built without sensitive environment variables

Name Link
🔨 Latest commit 04b13c9
🔍 Latest deploy log https://app.netlify.com/sites/govuk-design-system-preview/deploys/65982b9aa67a930008c5315f
😎 Deploy Preview https://deploy-preview-3407--govuk-design-system-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@36degrees
Copy link
Member

I don't think that page is the right place to send anyone using the old frameworks, there's not enough context to explain how that page helps them.

We could send them to the 'Migrate from our old frameworks' guidance in the v4 docs, but we might need to either tweak those docs to highlight the fact that it's v4 or provide more context where we're linking.

I think my preference would be to remove the warning text entirely, or to de-emphasise it and move it further down the page.

@dav-idc
Copy link
Contributor Author

dav-idc commented Jan 8, 2024

Hey @36degrees fair enough, any fix that means there's no longer a broken link is good.

Would it make sense to close this ticket , or keep it open and just change it so that the sentence is fully removed?

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.

None yet

2 participants