Header and Footer

Edit your header or footer

Your header and footer are shared layout areas. Changes you make there can appear across multiple pages on the published site.

Common header edits

• Update the logo or business name.
• Published header logos link to the website homepage by default.
• Edit navigation menu links.
• Full-width mega menus use the available browser width on the live site while still respecting their saved maximum width and a small edge gutter.
• Change the main call-to-action button.
• Adjust spacing, alignment, colors, and mobile behavior.
• Configure sticky or on-scroll header behavior, including the surface color, border, shadow, width, and compact spacing used before and after scrolling.
• Use inverse header tone when the header sits over a dark or image-heavy section and needs alternate logo or menu colors.
• Use the Menu Widget when you need to change menu items, dropdowns, or mobile menu styling.

Common footer edits

• Update contact details, disclaimers, copyright text, and social links.
• Add or remove footer columns.
• Update footer buttons or navigation links.
• Adjust spacing, colors, background, and divider treatments.

Assistant and API-assisted updates

Connected assistants and API key workflows can help prepare shared header, footer, and navigation changes.

• In the Design workspace, Agent Bee can inspect and update navigation directly instead of rebuilding the header for a menu-only request.
• Header and footer updates are saved as a draft on a review page by default, so you can preview them before changing the shared live layout.
• Header, footer, and navigation draft edits preserve one another when they are prepared close together. If the reviewed draft changes again before it can be published, Hiveality stops and asks for a retry instead of publishing an older shared layout.
• Navigation edits can add, remove, reorder, or repoint menu items without rebuilding the entire header.
• Preset-based header updates can also tune navigation size, weight, letter spacing, bar padding, and the main button style while preserving the saved menu destinations. Presets use the matching light or dark navigation colors for the selected header tone, and their mobile hamburger includes the saved navigation items, subitems, and main button.
• Publishing a shared header, footer, or navigation change creates a rollback point first, so a previous version can be restored if the change is not right.
• Publishing only the selected shared area keeps any other unpublished header or footer draft available for its own review.
• Agent Bee can list recent shared-layout recovery points and restore a prior header, footer, or navigation state after approval. Hiveality saves the current shared layout first, so the restore can also be reversed.
• Header rebuilds preserve the existing navigation menu unless the request explicitly asks to rebuild navigation too. They also retain existing header behavior such as sticky, overlay, and mobile settings unless the requested design changes those settings.

Tips

• Header and footer edits are separate from a page-body copy rewrite.
• If a header or footer uses a Menu widget, open the Menu settings to edit navigation items.
• If a header uses an inverse tone, also review the Logo and Menu widgets so their inverse images and colors are set.
• Saving header or footer changes refreshes the shared public layout, but still review more than one live page before considering a global navigation change complete.
• If you only want to change one page’s body content, use Editing Pages instead.