Use node global context to get assetManifest

[colegoldsmith]

Relies on an Antora extension to set the assets-manifest object on the node global context

[mlr]

UI bundle preview build successful! ✅
Deploying preview to GitHub Pages.
Deployment successful! View preview

[colegoldsmith]

I realized we can't read the UI bundle files at this point in the Antora build because the 'build' folder isn't created until after the page composer step (where these handlebars helpers are used). The only way I see to access this assets-manifest file is using the uiCatalog in an Antora extension and somehow make that object available to this helper, thus the global context

[mlr]

@colegoldsmith looks like the Antora build was unsuccessful. It didn't post a comment back here due to the error being too long https://github.com/riptano/datastax-docs-site/actions/runs/9389755534/job/25857983644#step:11:51

oh – maybe because it needs the asset manifest extension in your other PR

[eric-schneider]

maybe because it needs the asset manifest extension

Yeah, the codependency between the UI and the extension creates a bit of a split-brain scenario between this PR and the one in datastax-docs-site.

[github-actions]

The preview build for this pull request has been cleaned up due to being stale.

Preview builds that were 2 weeks old or older were automatically removed to maintain a tidy GitHub Pages site.

You can rebuild the preview at any time by pushing a new commit to this pull request:

git checkout cache-busting-v2
git commit --allow-empty -m 'rebuild preview'
git push origin cache-busting-v2

[eric-schneider]

Note: This PR causes breaking changes, and depends on updated Antora extensions in https://github.com/riptano/datastax-docs-site/pull/190