There are multiple ways a library's docs are built in general, for all libs. Consider the most common methods:

a library author runs ./b2 doc/ (modifications go in that lib's own Jamfile, or other doc/ files)
the build_docs scripts you mention install pre-requisites, and then ultimately run ./b2 doc/ (modifications go in that lib's own Jamfile)
or, the build_docs scripts run a variation of doc/build_antora.sh ( see boostorg/url as an example. Modifications go in doc/build_antora.sh , or other scripts which are then called.)
all docs are built for an official release, with ci_boost_release.py .

If by "asciidoc + boostlook" you definitely mean "antora + boostlook" , there is an antora-specific section of ci_boost_release.py that is downloading and running scripts from website-v2-docs, which means customizations may well go into website-v2-docs.

If a library author is using "asciidoc + boostlook" , but not "antora + boostlook", then they should modify their own doc/Jamfile or other local doc configuration files.

Which are the exact libraries this applies to, "asciidoc + boostlook" ?

Replace Rouge with highlight.js for code styling #67

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions