The page is empty because its a new section I guess, press the "Next" button on that mostly blank page (the right arrow)

The settings for section chunking with HTML output are in doc/Jamfile:

  <xsl:param>chunk.section.depth=8                # Depth to which sections should be chunked
  <xsl:param>chunk.first.sections=1               # Chunk the first top-level section?
  <xsl:param>toc.section.depth=8                  # How deep should recursive sections appear in the TOC?
  <xsl:param>toc.max.depth=8                      # How many levels should be created for each TOC?
  <xsl:param>generate.section.toc.level=8         # Control depth of TOC generation in sections

See also https://boostorg.github.io/quickbook/doc/html/boost_doc_tools/parameters.html

Changing to chunk.first.sections=0 is too invasive (and would e.g. lead to the quick reference appearing on the same page as the TOC).

Chunking (splitting to separate HTML pages) can be disabled locally:

[block'''<?dbhtml stop-chunking?>''']

Indeed including that leads to the first example appearing on the "more_examples.htm" page, while subsequent sections still appear on their own individual pages. I'd say we want to do this change:

Mmm. Sadness:

1. I was potentially too quick. Apparently the behaviour I described was only at partial rendered documentation, after completing the local rendering, all the "More HTTP Examples" appeared on a single page, which is not what we wanted
2. The "Quick Start" (1_quick_look.qbk) appeared to have this stop-chunking directive but with a typo. "Fixing" the typo sadly shows the same behaviour of squashing all descendant sections to the single HMTL:
   

The best I think we could do, then, is manually create some placeholder context on the main section page, perhaps with a bespoke hyperlink that duplicates what the "Next" button does in context...

Yeah its not perfect..

We tried to fix that before. I don't even remember in what library.

IIRC, the problem is we can't control the TOC depth for individual sections and the reference has subsections that look bad in the TOC.

If that's the case, the best solution would be to adapt docca to generate a document hierarchy that looks betters in the TOC.

Yes, I think it would be good enough to have a local TOC with the subitems from the parent page and a link back to the parent page.

As-is, if I copy the link from the main page and send it to a colleage, then the colleage could be lost because there's no information on the page linked and navigation by icons in the top right isn't clear (no text) and, when they opened the direct link, they can't just press the browser's back button to work from the parent page. So having the local TOC would help to navigate around the documentation.

Just as a reference, this is what happens when we remove the blank page: