Help4 Builder Header and Footer Launch Tutorial
Before the first click
Confirm what you are editing and where each kind of change belongs.
Read the page or template title first, select the exact element in the canvas or Navigator, then use the inspector tab that matches the job. This prevents a content change from becoming an accidental layout change.
Content
Change words, links, images, icons, data sources, shortcodes, and element-specific information.
Design
Change colors, typography, spacing, borders, radius, alignment, states, and desktop, tablet, or mobile values.
Advanced
Change labels, anchors, classes, attributes, visibility rules, motion, and other expert controls.
Page Settings
Use page-wide history, globals, publishing, template assignment, and recovery controls instead of editing one element.
Visual orientation
Match the screen before following the steps.
Open each image at full size. The numbered notes explain what the screen controls and what to confirm before changing customer content.
Screen 1
Theme Builder assignments
Review reusable headers, footers, content shells, archive templates, 404 output, conditions, and priorities.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 2
Theme Builder
Create global headers, footers, 404s, page shells, canvas landing pages, popups, and display conditions.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 3
Current Studio workspace
See the element library, device controls, live page frame, inspector, performance guidance, and save state together.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 4
Builder Studio
Use the live page frame, element library, template library, inspector, responsive controls, performance guidance, and save state in one workspace.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 5
Templates in Studio
Browse reusable structures and choose an insertion or replacement path intentionally.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 6
Template Library
Search page-purpose starters, insert a section, or deliberately replace a page instead of beginning from an empty screen.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Watch the real workflow
Watch the clicks before making the change.
Use the narrated walkthrough first, then follow the written steps and verification checks on this page.
Lesson 12
Commerce Products, Quantity, and Checkout
Create a native product, configure purchase and quantity rules, and verify the checkout and order path.
Read the complete transcript
- Open Native Products
Open Commerce, then Products. Native Catalog mode lets you create simple, service, digital, booking, variable, and subscription products without adding a separate store plugin.
- Describe the Product
Set the name, SKU, status, price, stock, description, image, tax behavior, fulfillment, and customer requirements. Use variants when options need their own price, stock, image, or SKU.
- Set Quantity Rules
Turn off customer quantity when a configured package must stay one unit per cart line. Customers can still add another separately. Use the order-limit option only when the whole order may contain one.
- Test the Full Order
Run a test from product display through cart, payment routing, confirmation, inventory, customer record, and order status. Verify both normal quantity products and fixed one-per-line products.
Lesson 8
Headers, Menus, and Mobile Navigation
Read the complete transcript
- Create a Header Template
Open Theme Builder and create or edit a header template. Reusable headers belong here so one controlled update can reach the assigned parts of the site.
- Insert the Menu Widget
In Studio, search the widget library for Menu. Insert the native component, then select the WordPress menu you want visitors to use.
- Configure Navigation
Set desktop orientation, dropdown behavior, submenu spacing, mobile breakpoint, and the compact menu trigger. Check that pointer and keyboard users can reach every submenu item.
- Assign and Test
Save the template conditions, then test a normal page on desktop and mobile. The mobile trigger should be visible, named, and able to open and close the complete menu.
Site shell workflow
Treat shared chrome as a product, not leftover decoration.
The header and footer frame every normal request. A small mistake there repeats across the entire site, so assignments and responsive behavior need their own launch matrix.
No duplicate shell
Every request should receive one winning header and footer.
No inaccessible dropdown
Hover, focus, keyboard, and touch users need a stable path into every submenu.
No hard-coded customer brand
Distributed Help4 Blank starts neutral; site-specific logos and contact details belong to the site configuration.
Guided walkthrough
Make one verified change at a time.
Each step includes the action, why it belongs in this order, and the checkpoint to verify before moving forward.
-
Preserve the exact logo
Use the approved media attachment and intrinsic proportions; do not regenerate, recolor, crop, or substitute a visually similar mark.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe preserve the exact logo result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Build native navigation
Use WordPress parent/child menu hierarchy so desktop dropdowns, keyboard focus, and the mobile menu share one source.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe build native navigation result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Fix the pointer path
Keep the submenu open while a pointer moves from its parent trigger into the dropdown and close only after focus/pointer truly leaves.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe fix the pointer path result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Build mobile controls
Provide one visible hamburger button, expanded state, close action, focus behavior, readable panel width, and no page overflow.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe build mobile controls result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Complete the footer
Add organization name, contact/support route, important services, privacy, terms, accessibility, social profiles, and an automatic year or year range.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe complete the footer result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Assign conditions
Use entire-site defaults with explicit canvas, checkout, protected, or campaign exclusions and resolve overlaps through priority.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe assign conditions result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Run the route matrix
Check home, page, post, custom post, archive, search, 404, checkout, logged-in state, desktop keyboard, touch, 390px, and 360px.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe run the route matrix result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
How to know it worked
Verify the edit in Studio and on the real page.
A successful edit stays visible when the element is reselected, matches the intended responsive view, survives publish, and appears on the public URL without clipping or lost styling.
Studio preview
Reselect the element and confirm the saved value and visual result are still present.
Responsive preview
Check desktop, tablet, 390px, and 360px widths for overflow, squeezed controls, and inherited values.
Public page
Open the public route in a new tab after publishing and confirm content, interactions, assets, and spacing.
Recovery
If the result is wrong, stop editing and use History or a known-good revision instead of rebuilding the page.
Avoid the expensive mistakes
Stop when the page stops behaving predictably.
More edits do not repair a bad state. Preserve the evidence, return to a known revision, and reproduce the smallest failing action.
Changing several controls at once
Change one content, design, or responsive value, then confirm it in the preview. A small edit is easier to understand and recover.
Editing the wrong layer
Use Navigator and read the inspector heading. Deleting a parent section can remove every child even when the selected text or image looked harmless.
Checking only desktop
Review tablet, 390px, and 360px before publish. Width, gap, padding, type, alignment, controls, and menus can inherit differently.
Publishing before values persist
Reselect the element and reopen the responsive view. If the value disappears or another tab has a newer revision, reconcile it before publishing.
Continue learning
Use the next guide that matches the work in front of you.
The full tutorial hub remains available without repeating dozens of unrelated cards on this page.
Start here
Install and setup
Download the ZIP, activate Builder Suite, understand the blank-theme path, and run the first clean check.
First page
Build a page safely
Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.
Editor controls
Know which tab changes what
Use Content for information, Design for appearance and responsive values, and Advanced for identity, attributes, visibility, and motion.
Recovery
Edit without losing work
Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.
Responsive
Control every viewport
Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Need help with this step?
Send Help4 the page, screenshot, or site goal.
Include the URL, what you are trying to build, what looks wrong, and whether this is a draft, staging site, or live customer page.