Fix broken xref targets with page-aliases #481
Merged
+2
−1
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.
We were getting build errors in cloud-docs from recent updates to schema reg auth in the docs repo. Here's why: The cloud-docs pages include content from the main docs repo via include::ROOT:... That included content contains xrefs like xref:manage:security/authorization/acl.adoc[...] which are valid in the docs repo, but those paths don't exist in cloud-docs.
By adding page-aliases to the cloud-docs pages, if something tries to link to manage:security/authorization/acl.adoc, we redirect it to security:authorization/acl.adoc (which is where that page actually lives in cloud-docs).
Add page-aliases to resolve xrefs from included ROOT content:
Description
Resolves https://github.com/redpanda-data/documentation-private/issues/
Review deadline:
Page previews
Checks