Closed odlp closed 2 years ago
Hi @odlp, sorry it took so long for us to get back to you!
I'm reviewing these changes now so we can get them merged, they look great to me, only thing is that they need to be rebased. I can do this locally, but I'm unable to push to your pull request.
Are you happy to do the rebase?
Alternatively, you can give maintainers access to push changes, which might be easier for you!
Thanks @lfdebrux - PR rebased
You might also have some luck with using the relative links settings instead of http_prefix
, see issue https://github.com/alphagov/tech-docs-gem/issues/271#issuecomment-1042951634.
This change has been included in release v3.2.0.
I think there are some outstanding issues with http_prefix
, however this release also includes support for relative links and assets.
You can now configure your Tech Docs Template (TDT) to build your documentation site to use relative links to pages and assets.
Support for relative links and assets was introduced in pull request #291: Support sites deployed on paths other than "/" (by generating relative links).
Hello 👋
This PR fixes asset URLs for sites built for Github pages using the default URL (like the API catalogue), in which paths are prefixed with the repo name.
Changes
$govuk-assets-path
to be overriden by implementorshttp_prefix
settingContext
For repo-specific Github pages, the site is deployed with the repo name prefixed in the path, e.g.
https://alphagov.github.io/api-catalogue/
. We'd like to use Middleman'shttp_prefix
option to account for this path prefix, which will allow us to simplify and automate our build process.Our Middleman config looks like this:
With this PR all asset URLs correctly include the
/api-catalogue/
prefix, and we can avoid using Middleman'sactivate :relative_assets
feature.References
asset_path
/image-url
helpers!default
to allow overrideshttp_prefix
configued