Skip to content

Configuring Widgets in the Website Builder

A storefront page in BigLedger is a stack of widgets — a banner, a product slider, a block of text — and the Website Builder is where you place them, pick what each one shows and publish the result. This guide takes you from an idea to a published page: how a page is put together, how to add and set up a widget, three complete recipes, and the two-step save that catches most people out.

Your job, and the screen for it

The jobScreen or tabRead
Understand pages, addresses, headers and footersLayout Manager tile, then a pageHow a page is put together
Make a new pageClone on an existing pageMake a new page
Put a widget on a page and set it upDesign Panel › Elements, then Selected NodeSteps 1–5
Build a typical page end to endThe recipesHome page, About us, Products
Find the right widget for a jobWhich widget for which job
Send changes to the live shopPublishStep 5

Overview

GadgetSphere Online Sdn Bhd runs the group’s web shop. Before the year-end sale you want an announcement bar saying Free delivery on orders over RM 300, a slider of new-arrival smartphones on the home page, an About us page, and a product listing that opens each phone’s details. Each of those is a widget on a page. You drag the widget onto the page, fill in its settings in the Design Panel on the right — mostly by picking pages, categories and posts from lists — save each widget, preview the page and publish once.

Every widget is set up the same way; only its settings differ, and those are on the widget group pages.

Where it fits

BeforeThis pageAfter
You can open the Website Builder at all — User Permission ManagerBuild pages from widgets and publish themShoppers see the pages on the storefront
The things widgets show exist: products and categories in the catalogue, posts in the Content Management System, images in the Media Library, menus in Menu Manager

Screens and menus

Open the Layout Manager tile on the Website Builder dashboard and click a page. The page opens with the canvas on the left and the Design Panel on the right. Above the canvas, Layout switches between pages and Platform chooses which version of the page you edit. On the right are Clone, Preview and Publish. On the canvas, each widget carries an edit and a delete button.

The Design Panel has four tabs:

  • Elements — what you can drag onto the page: Row and Column under Layout Elements, then the widgets grouped by kind (Headers & Navigation, Banners & Sliders, Products & Categories…), each with a one-line description. The search box matches the name and the description — type carousel to find every slider.
  • Selected Node — the settings of whatever you clicked on the canvas.
  • Layout — the page’s own record: title, code, description, type and status.
  • JSON — the page as stored, for checking rather than editing.

Configuration

Before you can use it

  • CP Commerce Admin for your login, and a fresh sign-in after it was granted. Without it the page opens but Publish answers You don’t have permission to publish. Please log in with an account that has CP Commerce Admin access. See whether the Website Builder opens for a person.
  • The records your widgets will show. A product slider shows a category of products, an About us page shows a post, a header shows a menu list. Create them first: a picker can only offer what exists.

How a page is put together

  • A page has a Code, and the Code is its address. A page with the code about-us is at yourshop.com/page/about-us. You see the code in the Layout tab. Every setting that links to a page stores that address — /page/about-us.
  • The header and footer are shared pages of their own. A page names one header and one footer layout, and they appear above and below it on the storefront, so a menu change in the header reaches every page that uses it.
  • Each platform has its own copy of the page. Desktop and each mobile platform in the Platform list keep separate trees. A widget you add on desktop is not on mobile until you add it there too.
  • Rows and columns arrange widgets — and they work the opposite way from their names:
A Row stacks what you drop into it one above the other; a Column puts its contents side by side. To show two banners next to each other, drop them into a Column.

Make a new page

There is no blank-page button in the Website Builder: you make a page by copying one. (An empty page is made on the Layout Instance tab of CP Commerce Admin, and then opened here.) Open a page whose shape is close to what you want (for About us, any simple content page), click Clone, and fill in:

  • Name — what you see in the page list.
  • Code — the address. Use lower case and hyphens: about-us becomes /page/about-us. Choose it carefully; links to the page use it.
  • Layout Instance Header and Layout Instance Footer — the shared header and footer to show.

Clone saves the new page at once, before any Publish, with the original’s Status and Type unless you change them in the dialog: check both first, or a copy of a live page is live as soon as it exists. The copy opens straight away (Cloned Successfully) with everything the original had. Delete the widgets you do not want with the delete button on each, then add your own.

Step 1: Open the page and the right platform

Open the page and check Platform before you add anything. Most shops build desktop first, then switch the platform and repeat the steps for mobile.

Step 2: Drag the widget onto the page

In Elements, find the widget — for the announcement bar, search announcement or open Banners & Sliders — and drag top-banner-widget onto the page, into a Row or into a Column. When you drop it, it is selected and the Design Panel switches to Selected Node.

Step 3: Fill in the widget’s settings

Selected Node shows Name (rename it to something you will recognise, such as Year-end delivery bar), Type, Widget, then the widget’s own settings, then Style and Widget Config (JSON). For the announcement bar, type Free delivery on orders over RM 300 into Header text, pick a Background color and Color, and leave the rest empty.

Most settings explain themselves. These kinds work in ways worth knowing:

Kind of settingHow it works
A page (labels ending in page)Click the box and pick one of your pages from the list; it fills in the page’s address, /page/<code>. You can also type any link, such as https://… for another site
A record — menu list, category group, category, post, content category, media folder, activityClick and pick it by name; type in the search box at the top to narrow a long list. A saved record that is not in the loaded list shows as Not in the list — saved ID …; publish, then reload, before you replace it — a list can miss a record that still exists, and a reload loses unpublished changes
ColoursAny CSS colour: #E30613, rgba(0,0,0,0.6) or a gradient. The colour picker beside the box appears only when the box is empty or holds a plain hex colour, so it never overwrites a gradient
Lists of items (slides, cards, testimonials)Add item adds one; the arrows reorder and the bin removes. Anything an item held that the form has no box for is kept
JSONA few complex settings are typed as JSON. Invalid JSON shows JSON is invalid and is not saved

Where a setting takes several values it says Separate values with commas under the box. A link that is not one of the pickers — Redirection link on the announcement bar, for example — is typed: use /page/ and the page’s code for one of your pages, or a full https:// address.

In the per-widget forms, a text, record or JSON setting you leave empty is not saved, and the widget then does what it does by default; clearing one removes it again, and a tick box you untick is saved as off. Opening a widget and saving without changes leaves its stored settings exactly as they were. Some long-standing widgets’ own forms (below) work differently: the sign-in form, for one, saves every field it shows as soon as you change any of them, empty ones included.

Some long-standing widgets — the image slider, product slider, sign-in form, checkout and a few more — have their own form; the settings it does not cover are under More settings at its bottom.

Style takes CSS for the box around the widget — padding: 16px 0; or margin-top: 24px; — the quickest way to put space between two widgets.

Rich text and the Expand button

Where a widget shows formatted text — text-widget, the agreement label at checkout, the note on the return status page, card text in our-services — the setting is a rich text editor with bold, lists, links, images from the media library and video. Click Expand above it to write in a large editor; Save there copies the text back, Cancel leaves it as it was. On the canvas, a text-widget also offers Tap to add content, which edits the same text.

Step 4: Save the node

Click the round save button at the bottom of Selected Node (its tooltip says SAVE NODE). The canvas redraws the widget.

SAVE NODE does not reach the shop, and it does not survive a reload. It keeps the change in this browser tab only. Reload, close the tab, switch to another page under Layout or let the session expire before Publish, and every change since the last publish is gone — with no warning. The tab holds one page’s draft at a time.

If Widget Config (JSON) shows JSON is invalid, SAVE NODE does nothing at all. Fix the JSON first.

Step 5: Preview, then publish

Preview opens the page for the platform you are on, with your changes in it; Edit brings you back. Publish sends the page — every platform you changed in this session — to the shop and answers Successfully Updated.

Recipe: a home page with a promotion

About 15 minutes. On the home page, desktop platform:

  1. Announcement bar. Drag top-banner-widget to the top. Header text: Free delivery on orders over RM 300; Redirection link: /page/delivery-policy (your delivery-policy page’s address); Redirection link text: See terms; pick the colours. SAVE NODE.
  2. Hero slider. Drag slider-v2 below it. Under Add Images, add one entry per slide: paste the Image URL from the Media Library, set Link Type to the page option and pick the page the slide opens in Layout Instance (the sale page, say). SAVE NODE.
  3. New arrivals. Drag product-slider-v2 below. Title: New arrivals; Category Group (Label List Hdr): your product categories; Category (Label Hdr): Flagship smartphones; Number of Visible Items: 5 for web, 2 for mobile. SAVE NODE.
  4. Preview, then Publish. Switch Platform to each mobile platform and repeat.

Recipe: an About us page from a post

About 10 minutes, once the post exists.

  1. In the Content Management System, write the About us post with its text and photo.
  2. Open a simple content page, Clone it with Name About us and Code about-us, and delete the widgets the copy brought along.
  3. Drag static-page-display onto the page. Post: pick About us; tick Display photo to show the post’s photos. SAVE NODE, Preview, Publish.
  4. Link to it: wherever a menu or button asks for a page, pick About us — it fills in /page/about-us.

To change the text later, edit the post; the page loads the post each time it opens, so there is nothing to republish.

Recipe: a product listing and its details page

Product widgets open a product on a product details page, which shows the product named in the page address. Several of them — both product sliders, category-filter-product-list and my-wishlist — fall back to the page with the code product-details when you leave their details page empty. Give your details page that code and you never have to set it.

  1. Details page. Clone a page with Code product-details, delete its widgets, drag product-details onto it, and set Checkout page to your checkout page. SAVE NODE, Publish.
  2. Listing page. On the page that lists products (Code smartphones, say), drag category-filter-product-list. Category group: your product categories; Category: Flagship smartphones; tick Show filter for the filter bar above the products. Web cols and Mobile cols are the width of each product out of 12 — 3 gives four products per row, 6 gives two. SAVE NODE, Preview — click a product and check its details page opens — then Publish.

The storefront code has marked category-filter-product-list as deprecated since 2022, yet it is still in Elements and has a form of its own. Nothing in the code names a replacement; check with BigLedger before you build a new listing page on it.

Which widget for which job

You wantUseGroup
A thin announcement bar at the toptop-banner-widgetBanners & Sliders
A big rotating hero imageslider-v2Banners & Sliders
A row of products from one categoryproduct-slider-v2Products & Categories
A full product list with category filtercategory-filter-product-listProducts & Categories
One product’s pageproduct-detailsProducts & Categories
Search with filters and sortingpower-search-filterProducts & Categories
A page of written content (About us, policies)static-page-display (from a post) or text-widget (typed here)Posts & Articles / Content & Media
The site header with logo, menu, search and cartresponsive-header or general-headerHeaders & Navigation
The site footerfooterFooters
Sign-in and registrationloginAccount & Membership
The cart and checkoutshopping-cart, checkout-step-v2Cart & Checkout
A customer’s ordersorders-listing, sales-order-detailsOrders & Invoices

Fields

The fields of Selected Node that every widget shares:

FieldWhat to know
NameOnly a label for you, on the canvas and in the JSON tab; shoppers never see it. SAVE NODE accepts an empty name, so keep one to find your widgets later
WidgetRead-only. To change the kind of widget, delete the node and drag the other one in
StyleCSS for the box around the widget. A typing mistake is not reported; the browser ignores the rule
Widget Config (JSON)What is stored. The widget’s settings write into it; you can also edit it by hand. Invalid JSON blocks SAVE NODE silently

Each widget’s own settings are on its group’s page — see Related documentation.

Lifecycle and effects

  • Drop, edit, SAVE NODE — kept in this browser tab’s draft of the page, one tree per platform.
  • Preview — shows the draft and does not publish the page. The widgets in it are live, though: claiming a voucher or placing an order in Preview does it for real, so use a test account.
  • Publish — sends the whole draft in one update. If the page had not finished loading it refuses with This layout has not loaded yet, so it cannot be published. Please reload the page and try again. A server failure shows Oops! Seems like our servers are having trouble processing your request. Please try again after some time. — the draft is still in the tab, so try again.
  • Pickers save what the widget needs — a page as /page/<code>, a record as its ID — so pages published before the pickers existed keep working unchanged.
  • On the storefront each widget is loaded by its name from the same list the Elements tab shows; a page holding a widget name no longer on that list renders nothing in its place.
  • Two people editing the same page see no warning of each other. Each Publish sends the whole page as that person’s tab holds it, so agree who publishes a page, and reload it before you start editing.

Related applets

Troubleshooting

SymptomCauseFix
My change was there, now it is goneThe tab was reloaded or closed before PublishRedo it and publish before leaving the page
SAVE NODE does nothingWidget Config (JSON) holds invalid JSONFix or undo the JSON, then save again
A picker says Not in the list — saved ID …The record was deleted or belongs to another website — or it exists but is not in the list as loaded (posts: the first 1,000; a list that failed to load is empty)Publish what you have first (a reload loses unpublished changes), then reload; if it still shows, check the record before you pick a replacement. To keep the old value, leave it
A picker says The list is empty or could not be loadedNothing of that kind exists yet, or the list failed to loadCreate the record (category, post, menu list…) or reload the page
The page list in a page picker is shortIt offers the pages the Website Builder has loadedType the address instead: /page/ and the page’s code
The widget shows on desktop but not on phonesIt was added on a desktop platform onlySwitch Platform and add it there
Two widgets I wanted side by side are stackedThey are inside a RowMove them into a Column
You don’t have permission to publish…No CP Commerce Admin, or no sign-in since it was grantedUser Permission Manager, then sign out and in
The product details page is emptyIt was opened without a product in its addressOpen it by clicking a product, not directly
Selected Node shows only Style and Widget Config (JSON) for most widgetsYour shop may be running a storefront build from before the widget forms (November 2026)Edit the JSON by hand, or ask BigLedger support when your shop will be updated

Related documentation

The settings of every widget, one page per group:

Also: Website Builder and User Permission Manager.

Last updated on