Help4 Theme Builder Template Conditions
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
Open the correct page
Find the intended page and open Studio without confusing it with a reusable template or similarly named draft.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 6
Builder Pages
Find Builder-enabled pages, open Builder Studio, and keep drafts separate from live customer pages.
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 14
Theme Builder Conditions and Reuse
Create reusable site templates and assign them to the correct content without duplicate headers, footers, or archive output.
Read the complete transcript
- Choose the Template Role
Open Theme Builder and choose the job first: header, footer, page shell, post, archive, search, 404, popup, or canvas page. Giving the template one clear role keeps the same layout from appearing twice or being inserted once for every archive result.
- Build Reusable Structure
Open the template in Studio and insert only the reusable structure that belongs to its role. Keep page-specific copy in the page layout or dynamic fields. A global header or footer should not quietly contain content meant for one campaign or one customer.
- Set Narrow Conditions
Set scope, content type, includes, excludes, and priority as narrowly as the job requires. Start with a draft assignment, confirm a representative route, and avoid competing templates with the same priority. Specific exclusions should win when a checkout or canvas page needs a different shell.
- Test Assigned Routes
Check Studio and public output on a normal page, a matching singular item, an archive, search, 404, and mobile navigation where relevant. Confirm exactly one assigned template renders, required assets load, interactive controls work, and an unrelated route remains unchanged.
Lesson 10
Templates, Site Kits, and Safe Imports
Choose reusable templates or style packs, understand import modes, and protect existing page content during application.
Read the complete transcript
- Browse Templates
Open Templates in Studio to browse reusable sections and page structures. Preview the purpose and responsive shape before inserting anything into the current page.
- Review Site Kits
Site Kits coordinate colors, typography, buttons, spacing, and related templates. Choose a kit that matches the site's purpose, not only its thumbnail.
- Choose the Right Mode
Use style-only application when existing content and block IDs must remain. Use a starter-layout replacement only when you intentionally want to replace the current structure.
- Verify the Result
After applying a template or kit, check content, links, global styles, desktop, tablet, and mobile. Use history immediately if the selected mode changed more than intended.
Condition workflow
Start broad, then add deliberate exceptions.
Use one normal site shell, add only the exceptions the design requires, and test a representative route for every rule.
No duplicate shell
A request should render one winning header, footer, and content template.
Assets follow assignment
Assigned archive, search, and 404 templates need the same Builder assets as singular output.
Studio uses template layout
Editing a template must preview its own saved or draft layout, not the front page.
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.
-
Choose the role
Select header, footer, single, archive, search, 404, canvas page, popup, or reusable section based on the output job.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe choose the role result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Choose the scope
Use entire site only for true defaults; use singular, archive, search, 404, or content-type scope for targeted templates.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe choose the scope result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Add includes
Limit the template to approved post types, records, taxonomies, or routes when the scope is still too broad.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe add includes result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Add exclusions
Remove checkout, landing pages, protected content, or other intentional exceptions from a broad assignment.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe add exclusions result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Resolve priority
Give the narrower valid rule a higher priority and avoid equal-priority overlaps that are hard to explain.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe resolve priority result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Test the matrix
Check home, normal page, post, custom post, archive, search, 404, checkout, logged-in state, and mobile navigation.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe test the 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.