Building a Page from Modules

A modular landing page has a parent page and a list of direct subpages. Each direct subpage supplies a section, such as a help panel, cards or an accordion.

#Create or edit the landing page

  1. Open the parent Basic page in NationBuilder.
  2. Add the page tag subpage_layout in Settings > Tags and save.
  3. For the usual weaFV opening, add module:hero to the parent and fill in its Headline, Content and optional eyebrow/image. The parent becomes the first module.
  4. Add the remaining sections as Basic subpages of that parent.
  5. On each section page, add its module tag, fill in the fields described in its guide, enable Include in supporter nav, and publish when ready.
  6. Open the parent's Subnav pages screen to put those sections in the intended order. Preview the parent URL to see the assembled result.

The parent can render its own headline/content as the first section even without a module tag. Removing module:hero alone does not guarantee that the first section disappears. Keep the parent hero in place on the four existing page designs unless the design is being changed.

A section and its items are different levels

For example, a cards section is a direct child of the landing page. Its cards can come from that section's own children or from a separate source page. An accordion section has its own children for the questions and answers.

Landing page — subpage_layout + module:hero
  Cards section — module:cards; include in supporter nav
    Card destination one
    Card destination two
  Questions section — module:concertina; include in supporter nav
    Question one — heading and answer
    Question two — heading and answer

Only direct children enabled in supporter nav are selected as landing-page sections. Nested items are read by their module, so follow that module's instructions for content and order. Do not move the nested items up to the landing-page level.

For a plain text section, use a Basic child with no module: or layout: tag. Style, spacing and sidebar:subscribe tags can still be used on that section.

Visibility and ordering

Include in top nav controls the main menu. Include in supporter nav controls the landing page's direct module list. These settings serve different purposes.

To remove a direct module from the assembled parent, turn off Include in supporter nav, then check the parent preview. This does not make its own URL private. To keep component URLs out of search engines, use page_no_robots as described in Access and search visibility.

Reorder the parent's direct modules from the parent's Subnav pages screen. For an accordion, image group or gallery, manage the nested item's order under that module and verify the result in the parent preview. Cards with sort:newest or sort:alpha use their specified sort instead of manual order.

An Image Gallery used as the parent is a special case: its children become gallery items rather than separate landing-page modules.