Page anatomy: header, body, sections, and blocks

Documentation / Page anatomy and the managed editor

A regular Beeboo page keeps its header and body separate. The header presents the page identity and optional media. The body contains the page's main editable content. Shared navigation and footer content belong to the surrounding site presentation.

The managed hierarchy

JuBody is the wrapper around non-header page content. JuSection is a top-level body section. JuBlock is a content child inside a section, such as Text, Image, Buttons, or a Row.

A Row adds cells within that content hierarchy. It can contain several content types and controls the way those cells form columns at different screen sizes. A section's own columns are a separate layout choice.

This distinction determines what a toolbar changes. Deleting a block removes one item. Deleting its section removes the container and everything inside it. Moving a section carries its children, whereas moving a block changes that child's position within an allowed content area.

Recognize ownership

A template-bound page takes its shared structure from the template. Named editable areas hold page-specific content. Locked content cannot be treated as an ordinary local block, even if it is visible beside editable text.

A custom body uses source-based content instead of native body blocks. The visual editor preserves that source and does not offer normal body editing. Shared shell regions are protected there too.

Regular pages must retain a real persisted header block. A hero-looking body section is not a replacement. Shared chrome pages, including toplines and footers, are exempt from the regular page-header requirement.

Before editing, identify the selected container and ownership layer. See Templates and reusable content for inherited content and Design and styling for custom design.