Help4 Builder Site Kits and Starter Sites
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
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 2
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.
Screen 3
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 4
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 5
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 6
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.
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 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.
Site kit workflow
Import, inspect, personalize, then publish intentionally.
A kit provides structure and inspiration. The site owner still controls the logo, offer, content, media, menus, assignments, metadata, forms, and launch order.
No silent replacement
Existing pages, templates, menus, globals, and front-page settings stay unchanged unless the user explicitly applies that change.
Idempotent import
A repeated import recognizes kit-owned objects instead of creating duplicate pages and menu items.
No placeholder launch
Sample logos, contact details, links, prices, and images are removed before publication.
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.
-
Open Site Kits
In Builder Studio, open the Site Kits tab and choose a kit that matches the website job rather than choosing only by color.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe open site kits result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Choose the style option
Leave Apply style tokens off when the current global design must remain. Turn it on only when the kit palette, typography, spacing, and shape should become the new starting system.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe choose the style option result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Import as drafts
Run the kit import once and wait for the completion report. Confirm the created page, template, and menu IDs before editing anything.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe import as drafts result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Review the shared shell
Open the draft header, footer, 404, archive, and other templates; replace placeholder branding and confirm every condition before publication.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe review the shared shell result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Personalize each page
Replace sample copy, links, images, forms, proof, prices, contact routes, and dynamic sources while preserving the valid element tree.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe personalize each page result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Set navigation deliberately
Review the kit-owned menu, parent and child hierarchy, mobile trigger, destinations, and any pages that should remain outside primary navigation.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe set navigation deliberately result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Launch in a controlled order
Publish the shared shell and approved pages, set the front page only after verification, then test metadata, forms, menus, 404, desktop, tablet, and mobile.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe launch in a controlled order 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.