In content-based-routing.adoc, the following link on L172 in the section about Language specifics fails to resolve in the downstream version. In the downstream topic file ({{ ref-configuration-of-content-based-routing-conditions-for-other-scripting-languages.adoc}}), asciidoc codes the link as follows:

{link-prefix}:{link-content-based-routing}#example-basic-content-based-routing-configuration[basic configuration example]

Upstream the same link behaves as expected.

Not sure whether the problem results because the downstream build fails to resolve the upstream attribute (link-content-based-routing: 'configuration/content-based-routing.adoc'), or if the problem lies with the anchor ID. Or both.

The target ID does not match the downstream module ID for the topic, which is example-debezium-basic-content-based-routing-configuration
Not sure whether this is due to incorrectly updating the downstream file manually, rather than fetching it from the upstream branch. Because the ID is used both upstream and downstream, is it necessary to revert to the upstream anchor ID, or should Nebel account for that?

On the Customer Portal, the link is corrupted and targets the following URL:

https://access.redhat.com/documentation/en-us/red_hat_integration/2021.Q1/html-single/debezium_user_guide/%7Blink-content-based-routing%7D#example-basic-content-based-routing-configuration

A 404 error results.

The expected link target is:

https://access.redhat.com/documentation/en-us/red_hat_integration/2021.Q1/html-single/debezium_user_guide/index#example-debezium-basic-content-based-routing-configuration

UPDATE
Currently, the attribute that is specified in the link is not resolving downstream. As a result, in the content that is published on the customer portal the link resolves to https://access.redhat.com/documentation/en-us/red_hat_integration/2021.Q1/html-single/debezium_user_guide/%7Blink-filtering%7D#example-basic-filter-configuration-example

As noted earlier, it should target:

https://access.redhat.com/documentation/en-us/red_hat_integration/<version>/html-single/debezium_user_guide/index#example-debezium-basic-content-based-routing-configuration

which is defined in the source as:

// Type: concept
// ModuleID: example-debezium-basic-content-based-routing-configuration
// Title: Example: {prodname} basic content-based routing configuration
[[example-basic-content-based-routing-configuration]]
== Example: Basic configuration

Upstream, antora.yml defines the value of link-content-based-routing as configuration/content-based-routing.adoc.
However, downstream, it appears that the attribute is undefined.