Downstreaming is only partially using containers.
Running downstreaming requires installing local dependencies.

New analysis for Dev Spaces 3.3

• Release notes are out of the way. See: https://issues.redhat.com/browse/RHDEVDOCS-4539 and https://gitlab.cee.redhat.com/red-hat-developers-documentation/devspaces-release-notes
• Starting with Dev Spaces 3.3, upstream is extensively using Antora Collector to single-source content. We must adapt downstreaming.
• Antora Assembler is a promising solution to clarify which files are single-sourced.
• Started to work on it in https://gitlab.cee.redhat.com/red-hat-developers-documentation/devspaces-documentation

Upstream to downstream conversion using the Antora Assembler.

The Antora Assembler is a (new) Antora add-on library and extension that assembles content from multiple pages into aggregate documents, converts them to the specified output format, and publishes them alongside other files in the site.
https://gitlab.com/antora/antora-assembler

It could replace the antora-to-plain-asciidoc shell script and simplify drastically the upstream to downstream conversion.

Follow the path of this very promising project exploring the usage of the extension in a similar scenario (publish to Pantheon 1): https://github.com/ahus1/keycloak-antora

Also, explore Distributed Component Versions to handle downstream examples: https://docs.antora.org/antora/latest/distributed-component-version/

(Previously) desired solution:

We should rather use containers.

Workaround

Currently, running the following playbook ensures installing all dependencies: https://gitlab.cee.redhat.com/ffloreth/ansible-laptop/.
However, this playbook is only tested on Fedora 35, not on RHEL CSB.

Implementing a fully containerized workflow will probably require less resources and will be more predictible than porting the playbook to RHEL CSB.