Skip to content

Help4 Builder Template Library

Template library

Choose the starter closest to the customer problem.

The template library is organized around jobs: launch, support, commerce, local SEO, recent work, forms, documentation, and recovery flows.

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.

Current Help4 Builder template libraryOpen full-size screen

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.

Help4 Builder template library inside Builder StudioOpen full-size screen

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.

Current Help4 Builder Pages screenOpen full-size screen

Screen 3

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.

Help4 Builder Pages screen on a clean WordPress installOpen full-size screen

Screen 4

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.

Current Help4 Builder Studio workspaceOpen full-size screen

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.

Help4 Builder Studio editing a Help4 WordPress pageOpen full-size screen

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.

Open the written guide

Read the complete transcript
  1. 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.

  2. 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.

  3. 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.

  4. 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.

Starter strategy

Do not make every page start from the same layout.

A service page, product collection, support article, and release note need different structures. Pick by outcome first.

Launch starters

Use for first-site setup, landing pages, announcements, and service launch pages.

Commerce starters

Use for product collections, subscriptions, checkout support, and recovery pages.

Documentation starters

Use for tutorials, knowledge-base indexes, support articles, and release notes.

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.

  1. Search by the page goal

    Use words like service, product, support, local, recent work, launch, docs, or checkout.

    Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.

    Done whenThe search by the page goal result is visible, remains after reselecting the item, and has not changed unrelated content or styling.

  2. Preview the starter

    Confirm the starter has the right sections before importing it.

    Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.

    Done whenThe preview the starter result is visible, remains after reselecting the item, and has not changed unrelated content or styling.

  3. Import into a draft

    Use the draft to replace content and remove sections that do not fit.

    Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.

    Done whenThe import into a draft result is visible, remains after reselecting the item, and has not changed unrelated content or styling.

  4. Run mobile early

    Templates still need long headings, images, buttons, and cards checked on small screens.

    Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.

    Done whenThe run mobile early result is visible, remains after reselecting the item, and has not changed unrelated content or styling.

  5. Keep a best version

    Save cleaned-up versions as reusable patterns for future pages.

    Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.

    Done whenThe keep a best version 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.

Install Guide

First page

Build a page safely

Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.

First Page

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.

Controls Guide

Recovery

Edit without losing work

Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.

Recovery Guide

Responsive

Control every viewport

Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.

Responsive Guide

Templates

Choose a starter

Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.

Template Guide

Browse every tutorial

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.