Real Builder screenshots
The lab should show the product, not only describe it.
These screenshots anchor the feature list in the actual Builder Suite experience customers and support staff will use.
Builder shell
The lab starts with the real editing surface: page structure, settings, and a calmer way into page work.
Canvas editing
Customers can see sections, cards, calls to action, and page structure before they publish.
Context actions
Duplicate, move, style, remove, and adjust page pieces without hunting through a maze of settings.
Default icons
A useful starting icon drawer helps support, commerce, security, local service, and documentation pages launch faster.
Module lanes
Each feature has a job, and each job should stay compartmentalized.
The lab groups the plugin by customer outcomes so the site can turn on what it needs without dragging every module onto every page.
Build pages
Sections, cards, buttons, images, responsive controls, reusable templates, and blank-theme page structure.
Organize content
Search, structured fields, template specs, icon defaults, support content, and repeatable page patterns.
Sell and route
Product cards, catalog previews, checkout handoff, subscriptions, payment routing, and processor-aware support paths.
Protect launch
SEO, performance discipline, security posture, update readiness, release channels, and support escalation.
Live module
Search checks content and products from one customer-facing box.
This helps a customer find pages, products, tutorials, and support paths without needing to know where the item lives.
Live module
Product cards prove the commerce layer can render inside the builder flow.
Catalog previews belong in the same design system as service pages, support pages, checkout links, and landing pages.
Live module
Checkout handoff stays visible while the full bridge work continues.
The lab keeps checkout routing easy to inspect while the customer-facing checkout remains on the connected Help4 Network path.
Help4 Checkout
Use this as a starter shell and wire your front-end app to /wp-json/h4bs/v1/checkout.
Live module
Sliders and starter templates are tested where customers can actually see them.
The slider and template library checks make it easier to catch broken media, awkward spacing, and confusing starting points before release.
Live module
Template browsing should make the first page easier to start.
Templates are the difference between a blank builder and a practical path for business owners, agencies, and Help4 support builds.
Plain-language starters for headers, footers, 404s, page shells, canvas landing pages, service sites, support pages, SEO, commerce, subscriptions, payment routing, builder onboarding, and launch work. Service page for audits, fixes, readable forms, contrast, keyboard paths, and practical remediation. Best for: urgent fixes, site care, migrations, cleanup, support routing, and operational trust pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. 404 for account, download, and billing paths with login recovery, docs, latest download, and support escalation. Best for: missing pages that should recover visitors with search, support links, product routes, and helpful next steps. Use when: a broken or old URL should send people somewhere useful instead of dumping them into a dead end. Next step: copy the 404 spec, set the role and scope to 404, add search/support/product links, then test an old URL. Header pattern for service catalogs, documentation links, case studies, and account/support routes. Best for: global navigation, phone/contact bars, primary CTAs, service menus, and first-click trust on every page. Use when: the site needs a reusable top bar that makes the brand, offer, menu, and next action obvious on mobile and desktop. Next step: copy the header spec, set the role to Header, map the menu and CTA, then check wrapping at mobile width before publishing. Agency support page for design teams, freelancers, SEO teams, maintenance queues, and implementation overflow. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Footer for plugin, software, and digital-product sites with latest download, docs, changelog, and support links. Best for: sitewide closing sections, support links, policy links, local proof, newsletter CTAs, and final conversion paths. Use when: visitors reach the end of a page and still need contact options, trust cues, location/service links, and support routes. Next step: copy the footer spec, set the role to Footer, replace policy/support links, and make sure the columns collapse cleanly on mobile. Header for appointment-heavy sites with service picker, phone cue, booking CTA, and compact mobile navigation. Best for: global navigation, phone/contact bars, primary CTAs, service menus, and first-click trust on every page. Use when: the site needs a reusable top bar that makes the brand, offer, menu, and next action obvious on mobile and desktop. Next step: copy the header spec, set the role to Header, map the menu and CTA, then check wrapping at mobile width before publishing. Booking-first service page for consultations, repair calls, demos, estimates, and calendar-driven intake. Best for: urgent fixes, site care, migrations, cleanup, support routing, and operational trust pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Readable post/page template with table of contents, screenshot slots, steps, FAQ, and support escalation. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Portfolio starter for before/after screenshots, project notes, measured improvements, testimonial, and similar-work CTA. Best for: SEO landing pages, local service pages, proof sections, lead capture, and conversion paths. Use when: you need to show the real work, the problem, the result, and why someone should trust the next project to you. Next step: drop in screenshots, timeline, outcome metrics, and the final customer-facing call to action. Homepage starter made for the Help4 blank-theme workflow with global header, footer, content bands, and safe spacing defaults. Best for: sitewide closing sections, support links, policy links, local proof, newsletter CTAs, and final conversion paths. Use when: visitors reach the end of a page and still need contact options, trust cues, location/service links, and support routes. Next step: copy the footer spec, set the role to Footer, replace policy/support links, and make sure the columns collapse cleanly on mobile. Hello-style blank theme launch starter for global parts, display rules, responsive QA, and publish checklists. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: a buyer is comparing options and needs the differences, risks, and value explained without sales fog. Next step: replace the rows with real buyer objections, pricing anchors, decision criteria, and one primary consultation action. Booking starter for appointment requests, service choices, calendar expectations, deposits, and confirmation copy. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: checkout needs trust, clear steps, payment routing, and a clean handoff to the account system. Next step: explain payment steps, recovery paths, account access, and where the customer lands after checkout. Appointment-focused 404 with booking CTA, service selector, phone fallback, and common service links. Best for: missing pages that should recover visitors with search, support links, product routes, and helpful next steps. Use when: a broken or old URL should send people somewhere useful instead of dumping them into a dead end. Next step: copy the 404 spec, set the role and scope to 404, add search/support/product links, then test an old URL. For customers who send Figma, screenshots, sketches, copy, or rough instructions. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: a builder page needs structure, brand tokens, reusable sections, fields, media, or motion without bloating every page. Next step: copy the starter spec, set global styles, replace sample content, and confirm mobile spacing before launch. First-run starter for non-technical users who need a safe hero, proof, service cards, contact CTA, and publish checklist. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: you need to show the real work, the problem, the result, and why someone should trust the next project to you. Next step: drop in screenshots, timeline, outcome metrics, and the final customer-facing call to action. First-day builder starter for setup, blank theme pairing, starter selection, responsive checks, and publish path. Best for: large product catalogs, variation choices, product imports, and store pages customers can understand. Use when: a finished job needs proof, reviews, follow-up links, and a softer path back to the business. Next step: connect review destinations, add two or three proof points, and publish it as a follow-up link after completed work. No-header/no-footer landing template for campaigns, lead magnets, paid traffic, and focused offers. Best for: global navigation, phone/contact bars, primary CTAs, service menus, and first-click trust on every page. Use when: the site needs a reusable top bar that makes the brand, offer, menu, and next action obvious on mobile and desktop. Next step: copy the header spec, set the role to Header, map the menu and CTA, then check wrapping at mobile width before publishing. Case-study starter for problem, work performed, screenshots, measurable outcome, testimonial, and next CTA. Best for: SEO landing pages, local service pages, proof sections, lead capture, and conversion paths. Use when: a finished job needs proof, reviews, follow-up links, and a softer path back to the business. Next step: connect review destinations, add two or three proof points, and publish it as a follow-up link after completed work. Clean account/checkout bridge that sends buyers to Help4 Network without exposing internal billing labels. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Support and trust page for failed payments, abandoned checkout, webhook status, retry flows, and customer help. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Simple sitewide header with logo, primary navigation, phone/contact cue, and one clear service CTA. Best for: global navigation, phone/contact bars, primary CTAs, service menus, and first-click trust on every page. Use when: the site needs a reusable top bar that makes the brand, offer, menu, and next action obvious on mobile and desktop. Next step: copy the header spec, set the role to Header, map the menu and CTA, then check wrapping at mobile width before publishing. Post-purchase onboarding page for account access, site details, assets, contacts, and first ticket steps. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Account, invoice, ticket, and checkout bridge page that keeps billing language clean and branded. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Footer for product and subscription sites with account, checkout, refund, support, and delivery routes. Best for: sitewide closing sections, support links, policy links, local proof, newsletter CTAs, and final conversion paths. Use when: visitors reach the end of a page and still need contact options, trust cues, location/service links, and support routes. Next step: copy the footer spec, set the role to Footer, replace policy/support links, and make sure the columns collapse cleanly on mobile. Security starter for checkout trust, processor fallback, suspicious order review, backups, and site health. Best for: checkout routing, processor rules, payment confidence, and configured checkout handoff pages. Use when: customers need answers, setup steps, and support paths before opening another ticket. Next step: group the top articles by customer problem, link setup tutorials, and keep the support request path obvious. Buyer-guide starter for comparing plans, managed service levels, build options, risks, and next steps. Best for: a clean first draft when a customer needs a page structure they can hand off and publish faster. Use when: a buyer is comparing options and needs the differences, risks, and value explained without sales fog. Next step: replace the rows with real buyer objections, pricing anchors, decision criteria, and one primary consultation action. Client-friendly page for gathering copy, screenshots, files, goals, approvals, and launch-ready content. Best for: blank-theme builds, reusable templates, field groups, motion sections, and builder onboarding. Use when: a builder page needs structure, brand tokens, reusable sections, fields, media, or motion without bloating every page. Next step: copy the starter spec, set global styles, replace sample content, and confirm mobile spacing before launch. Content-planning starter for blog campaigns, service updates, launch announcements, social snippets, and SEO briefs. Best for: SEO landing pages, local service pages, proof sections, lead capture, and conversion paths. Use when: a local or service page needs search intent, proof, location relevance, and a clear next action. Next step: copy the starter spec into a draft, swap the examples for real content, then run the SEO and mobile checks. Service-area, quote-first starter for contractors. Best for: a clean first draft when a customer needs a page structure they can hand off and publish faster. Use when: a visitor needs a fast way to ask for help, request pricing, or explain what they need before talking to you. Next step: add service choices, location, urgency, budget, and route the form to the person who can reply fastest. Starter for courses, memberships, private content, lessons, pricing, and student outcomes. Best for: plans, memberships, renewals, trials, setup fees, and recurring checkout pages. Use when: a buyer is comparing options and needs the differences, risks, and value explained without sales fog. Next step: replace the rows with real buyer objections, pricing anchors, decision criteria, and one primary consultation action. No starter templates match that filter.Starter Template Library
Accessibility Remediation Page
Spec outline
Account Login Rescue 404 Template
Spec outline
Agency Mega Menu Header Template
Spec outline
Agency Overflow / White-Label Page
Spec outline
App Download Footer Template
Spec outline
Appointment Booking Header Template
Spec outline
Appointment Booking Page
Spec outline
Article and Tutorial Page Template
Spec outline
Before After Portfolio
Spec outline
Blank Theme Homepage
Spec outline
Blank Theme Launch Page
Spec outline
Booking Request Page
Spec outline
Booking Rescue 404 Template
Spec outline
Build From Design Page
Spec outline
Builder First Page
Spec outline
Builder Quickstart Home Page
Spec outline
Canvas Landing Page Template
Spec outline
Case Study Page
Spec outline
Checkout Bridge Page
Spec outline
Checkout Recovery Page
Spec outline
Clean Service Header Template
Spec outline
Client Onboarding Checklist
Spec outline
Client Portal Bridge Page
Spec outline
Commerce Account Footer Template
Spec outline
Commerce Security Hardening Page
Spec outline
Comparison Buyer Guide Page
Spec outline
Content Brief Workflow Page
Spec outline
Content Calendar Page
Spec outline
Contractor Services Starter
Spec outline
Course / Membership Page
Spec outline
Release check
Use the lab before cloning staging live.
Check the screenshots, search, products, checkout handoff, slider, and template library on mobile and desktop. If a module breaks here, fix it before calling the public release clean.