Update multi-page navigation to allow custom path prefix #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently if the tech-docs is deployed on a path (e.g.
https://alphagov.github.io/api-catalogue/) the navigation links are broken as they are generated from root (/). One way to avoid this without affecting current single-page or multi-page configuration is to define apath_prefixin config that is prepended to each link.This is an attempt to fix #128 which is currently blocking any deployment for the api-catalogue.
I'm open to any other suggestions that will unblock this - especially since I'm not familiar with this project or Middleman.
Note: I needed to refactor the conditional statements as linter was complaining about the code having too many lines (
Metrics/BlockLength: Block has too many lines. [31/25])