-
Notifications
You must be signed in to change notification settings - Fork 339
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
Redirect Sass docs in review app to Sass API reference in Frontend Docs #1892
Comments
@36degrees Our 'CSS Style Guide' doc contains a link to http://govuk-frontend-review.herokuapp.com/docs:
Should the link in the above quote go to https://frontend.design-system.service.gov.uk/sass-api-reference/#sass-api-reference instead? |
@EoinShaughnessy yes, I think it probably should! Great catch. I don't think we should call it a 'SassDoc application' if we change the link though, and the wording could be clearer… maybe something like:
|
It's also odd that we link 'SassDoc' to the specific SassDoc documentation on file level annotations. That doesn't make sense to me – it should probably just link to the SassDoc homepage? |
@36degrees Thanks! That wording looks good. I'll raise a PR, separate to this issue, that includes both your wording and a link to the SassDoc homepage. |
When running on Heroku (based on the presence of the `HEROKU_APP` environment variable set in `app.json`): - link to the live API reference docs from the homepage of the review app - redirect requests for `/docs` to the live API reference docs This avoids the confusion of having two ‘live’ versions of the Sass docs available, whilst redirecting anyone who may have the existing docs bookmarked. However, it’s still useful to be able to run the 'generic' Sass docs locally so that we can use it to preview documentation before we do a release. As such, when running locally: - link to both the live API reference docs and the ‘local’ docs from the homepage of the review app - preserve the existing behaviour of serving the locally generate Sass docs when visiting `/docs` Closes #1892.
When running on Heroku (based on the presence of the `HEROKU_APP` environment variable set in `app.json`): - link to the live API reference docs from the homepage of the review app - redirect requests for `/docs` to the live API reference docs This avoids the confusion of having two ‘live’ versions of the Sass docs available, whilst redirecting anyone who may have the existing docs bookmarked. However, it’s still useful to be able to run the 'generic' Sass docs locally so that we can use it to preview documentation before we do a release. As such, when running locally: - link to both the live API reference docs and the ‘local’ docs from the homepage of the review app - preserve the existing behaviour of serving the locally generate Sass docs when visiting `/docs` Closes #1892.
When running on Heroku (based on the presence of the `HEROKU_APP` environment variable set in `app.json`): - link to the live API reference docs from the homepage of the review app - redirect requests for `/docs` to the live API reference docs This avoids the confusion of having two ‘live’ versions of the Sass docs available, whilst redirecting anyone who may have the existing docs bookmarked. However, it’s still useful to be able to run the 'generic' Sass docs locally so that we can use it to preview documentation before we do a release. As such, when running locally: - link to both the live API reference docs and the ‘local’ docs from the homepage of the review app - preserve the existing behaviour of serving the locally generate Sass docs when visiting `/docs` Closes #1892.
When running on Heroku (based on the presence of the `HEROKU_APP` environment variable set in `app.json`): - link to the live API reference docs from the homepage of the review app - redirect requests for `/docs` to the live API reference docs This avoids the confusion of having two ‘live’ versions of the Sass docs available, whilst redirecting anyone who may have the existing docs bookmarked. However, it’s still useful to be able to run the 'generic' Sass docs locally so that we can use it to preview documentation before we do a release. As such, when running locally: - link to both the live API reference docs and the ‘local’ docs from the homepage of the review app - preserve the existing behaviour of serving the locally generate Sass docs when visiting `/docs` Closes #1892.
What
Redirect from http://govuk-frontend-review.herokuapp.com/docs to https://frontend.design-system.service.gov.uk/sass-api-reference/#sass-api-reference
We may need to provide a way to run the 'generic' Sass docs locally so that we can use it to preview documentation before we do a release.
Why
Avoid the confusion of having two versions of the Sass docs available, and point anyone who may have the existing docs bookmarked to the new docs.
The text was updated successfully, but these errors were encountered: