Help4 Builder Default Icon Library

Template Library
Start from page-purpose templates instead of staring at a blank canvas.

Builder Studio
Build the page visually with responsive controls, element panels, performance guidance, and a live preview.

Settings dashboard
Confirm modules, setup wizard state, support links, release channel, and the main Builder Suite shortcuts before building.
Icon usage
Icons should clarify the card, not decorate the page into noise.
Use one icon per feature card or process step. Keep labels plain and do not use icons as a replacement for important copy.
Builder icons
Use quickstart, template, module, responsive, and launch icons for setup pages.
Commerce icons
Use catalog, variation, subscription, payment route, and checkout icons for store flows.
Support icons
Use ticket, docs, health, uptime, email, and emergency icons for help paths.
Step
Pick the card purpose
Choose the icon after the card title and benefit are written.
Step
Use local defaults first
The bundled set avoids dependency on a third-party icon CDN.
Step
Keep labels clear
The icon supports the label; it should not be the only explanation.
Step
Check contrast
Icons should remain visible in dark and light sections.
Step
Preview mobile
Icons should not squeeze the copy or enlarge cards unpredictably.
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.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Theme layer
Headers and footers
Use Theme Builder for global headers, footers, 404s, page shells, canvas pages, popups, and conditions.
Fields
Structured content
Use fields when content repeats: FAQs, service areas, specs, team members, galleries, relationships, and product data.
Commerce
Products and payments
Plan catalog data, variations, subscriptions, checkout context, and payment routing before launch.
Capture leads
Forms and sliders
Use forms and motion only where they support the page goal and do not load extra assets everywhere.
Launch QA
SEO, speed, security
Check metadata, schema, readability, AdSense-style quality, Analytics intent, SSL, headers, images, and mobile.
Proof
Website Snapshot
Turn public URLs into safe website screenshots for recent work, migrations, support notes, and launch recaps.
Release safety
Updates
Use stable live packages and md beta testing to keep Builder Suite ready for the next WordPress line.
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.
