Skip to content

Working with Sections

Sections are the building blocks of your pages. Understanding how to work with them effectively makes content management smoother.

Use clear, consistent naming:

  • Page-specific: home-hero, about-team, services-list
  • Reusable: global-cta, newsletter-signup, footer-contact
  • Temporary: holiday-banner-2024, campaign-spring

When creating a new section:

  1. Check if one already exists — Reuse before creating
  2. Use descriptive titles — “Homepage Hero” not “Section 1”
  3. Match the slug to the component — Ask your developer what the component is called
  4. Add a description — Note where it’s used and what it contains
graph LR
    A[Create Section] --> B[Add Content]
    B --> C[Attach to Page]
    C --> D[Publish]
    D --> E[Edit as Needed]
    E --> F[Deactivate when Done]

The power of sections is reusability. A section can appear on multiple pages:

SectionUsed On
Newsletter SignupHome, About, Blog
Contact CTAServices, About, Pricing
Trust BarHome, Landing Pages

When you edit a reusable section, changes appear everywhere it’s used.

Drag and drop blocks to reorder them within a section. The top-to-bottom order in the builder matches the top-to-bottom order on the frontend.

Each block shows a preview label based on its content. This makes it easy to identify blocks at a glance:

Section: About Hero
├── Heading: "About Our Company"
├── Paragraph: "We are a team of..."
└── Image: team-photo.jpg

Click the block header to collapse/expand it. This helps manage sections with many blocks.

  • Heading block (H1)
  • Paragraph block (intro text)
  • Optional: Image block (background)
  • Multiple heading blocks (H3)
  • Paragraph blocks (descriptions)
  • Optional: Icon or image blocks
  • Heading block (H2)
  • Paragraph block (value proposition)
  • Custom CTA block or rich text with links

When you need a new section type:

  1. Describe the content fields you need
  2. Show an example or mockup
  3. Specify where it will be used
  4. Ask for the component name (slug) to use

See Collaborating with Developers for more.