Planning checklist, measured editor cost, and what happens when you stack APB parents.

APB-DOCS-ADVANCED

Capabilities shows leftover options one theme at a time. Advanced Pages on the demo stacks parents, placements, JS libraries, overlays, chrome, and item counts until the runtime has to choose. Probe result on 2026-09-02: 70 pass, 0 fail. Use this checklist before writing a brief or a rebuild script.

Planning checklist

  1. Host type. Basic page for unmoderated English composition. article only if you need Editorial workflow. international_page only if you need Content Translation. Do not enable workflow or translation on page.
  2. Parent list, not a tree. List apb_pb_* parents in field order. Nesting a band inside another band means target placement into a simple-content region item whose title is a seeded locator, with that region parent earlier in the field.
  3. Placement term per parent. Default is Body. See the placement matrix. Overlay content cannot be placed.
  4. One JS library family per concern, but many instances. Two slideshows means two Splide roots. Duplicate overlay trigger IDs last-write-wins. Ask for unique field_apb_pi_trigger_id values on a page.
  5. Chrome. Width tokens below 100% center with !important. Container JSON lengths need units. Opacity is 0–1. Slideshow chrome is spacing only.
  6. Editor cost. The Legacy paragraphs widget opens every parent. Kitchen sink on the demo: 17 parents, edit form about 2.1 s and 1.17 MB HTML, 187 IEF hits. Prefer several URLs over one twenty-parent node unless the point is density. Rebuild with a script; node IDs change.
  7. Do not put overlay JSON, links overlay, or profile modals on a node with a forward draft and expect the published revision to be what anonymous JSON returns. Do not expect overlay JSON to vary by language after a cached hit.

Interactions worth expecting

  • Slideshow + carousel + simple-content images = three Splide families.
  • Overlay content + links overlay + profiles + gallery + video = five GLightbox entry points. Overlay content reuses window.__apbGlightbox.
  • Hash from a tabs or feature-box body opens overlay content (document-wide a[href*="#"]). A hash on another URL navigates away.
  • Feature box height token is not a min-height; copy can clip.
  • Vertical tabs become an accordion on a phone (component JS).
  • A 100vh Top-region slideshow sits below the stacked theme header, so it is not a full-bleed first fold on a phone.
  • Infinite logos does not accept SVG — rasterize to PNG.
  • Slideshow background video is media type video, not remote_video.

Live lab: demo.apb.aero.net/advanced.