CMS-first rule

Public marketing pages must be created and remain editable in the CMS page builder. Use theme files for reusable rendering and design-system behavior—not for hardcoded page copy, menus, images, or one-off page structure.

What a new site starts with

Chosen at Shape your workspace. Example content gives a homepage, an About Us, a Privacy Policy and Terms of Use under a Legal category, and a ready-made set of menus: a top bar, a header with Store, Resources, Knowledgebase and Updates mega menus, four footer columns and the legal links. Nothing but the homepage gives one homepage and no menus at all. Every page is editable in the builder and every page can be deleted.

Supported sections

Fifty-five section types, grouped in the section library as Hero, Commerce, Giving, Content and Media. Each is described, with its fields, in Page builder sections. Banner does everything Slider does and more; Slider stays supported for pages that already use it. Since 1.11.0 an active add-on can offer sections of its own, listed under their own heading in the library; see Sections from add-ons.

Since 1.10.0 Content Manager › Menus holds every menu on the website, one tab each. It replaces the Main Menu, the Mega Menu Builder, the Footer Links page and the four "Sub Menu" slots in the footer settings, and needs the Manage Content permission.

Header
The main navigation, up to three levels deep. Each top-level item opens as a plain link, a dropdown or a mega menu.
Top bar
A slim row above the header for quick links such as support, contact and sign in. It shows whenever it has items.
Footer columns
Each top-level item is a column heading; the items inside it are that column's links.
Footer bottom strip
The small links beside the copyright: privacy, terms, cookies.

The panel on the right adds a WBAMS section (Knowledgebase, Updates, Events, Gallery, Downloads, Store, Pages, Contact, Support, Sign in and others), a Content Manager page, a link, a heading group or, inside a mega menu, a featured card. Drag a row by its grip to reorder it, and drop it onto another to nest it; Move up, down, in and out in the item's settings do the same from the keyboard. Each tab is saved on its own.

Every item can carry an icon, a picture from the media library, a description, a badge, open in a new tab, a CSS class, a column width in a mega menu, who sees it (everyone, signed-in visitors or signed-out visitors) and a translated label for each site language. A link to tel:, mailto:, sms: or any other address with a scheme of its own is used as it is; javascript:, data: and vbscript: links are refused.

Since 1.13.4 a top-level header link can be shown as a button, for the one thing visitors should do first, such as Book online; the list marks it Button. Serepok draws it as the site's main button, keeps it in view when other items move into More, and puts it beside the menu button on phones and tablets.

Mega menus

A mega menu has seven layouts: Columns, Featured + columns, Cards grid, Tabs, Compact list, Showcase (picture tiles for news, albums and events) and Spotlight (one large item beside a short list). Its settings cover the number of columns, the width, icons, descriptions, pictures, an intro panel, a "Go to" link, and the featured card's title, text, picture and button. Menu pictures are sent as small thumbnails rather than the full upload.

Automatic or manual

A WBAMS section added to the header or the footer can fill itself in: the Knowledgebase with its categories and articles, Updates with the latest news, Events with the next events, the Store with its product groups and products, and so on. Settings choose all groups or only ticked ones, how many groups, how many items in each, the order, whether headings link to their pages, a "View all" link, and items without headings; a preview shows what the website will show. New articles, updates and events then appear without editing the menu. Switching an item to Automatic offers to remove the items that were added under it by hand, all at once. A section switched off under Website Sections leaves the menu on its own.

Upgrading from before 1.10.0

The site's existing menus are copied into the builder once, the first time Content Manager › Menus is opened: the mega menu when it was on (with its translations, subtitles, pictures and column widths), otherwise the main menu, plus the footer links and, when they were switched on, the footer's sub-menu links. The website looks the same until the menus are changed. Opening the page also creates the builder's own table, so the database user must be allowed to create tables.

Both client themes draw the same menus, including the phone menu, in light and dark mode, and the menu marks the page the visitor is on — since 1.11.0 also on pages reached through index.php?rp=, where an article or post also marks its section.

Back to top button

Since 1.10.0 Draisap shows a button in the lower right corner once a visitor has scrolled down a page. It glides back to the top — or jumps there for visitors who turn off animations — and moves the keyboard focus to the page content; it follows light and dark mode and stays clear of a phone's rounded corners. Content Manager › Footer Layout › Back to Top Button turns it on or off, and Serepok's button in the footer follows the same switch. It is on by default.

Publishing

A page is draft, scheduled or published, chosen from the Status control in the builder header. Saving does not publish: a draft can be built and saved as often as needed and stays invisible to visitors, though an administrator can preview it. A scheduled page carries a date and time and goes live on its own within a minute of it — the check runs on ordinary client-area traffic, so no cron job is needed for it. Only a published page is served, listed in the sitemap or reachable by its address.

Every save stores a revision: the page and all of its settings as one document. Revisions in the builder lists the last twenty with who saved them and when, and Restore puts one back exactly as it was. The restore is itself a save, so it can be undone the same way.

Saved blocks and page templates

The bookmark on any section saves it under a name. Saved blocks appear in the section library under the Saved filter and are inserted as a copy, so a block is a starting point rather than a live link: editing the saved block changes what the next insertion starts from, not the pages already carrying it. Remove a saved block from the library with its own remove control; the pages that used it are unaffected.

Any page can be marked as a Page Template in its settings. Template pages are not served and are not in the sitemap; they exist to be copied. The Page Manager's Add New button lists them, and a page created from a template starts with the template's sections, language and settings under a new title and slug.

Search and sharing

Each page's SEO panel holds its meta title and description, a canonical address, the Open Graph title, description and image and the Twitter card type used when a link to the page is shared, and its sitemap entry — excluded, or with a priority and change frequency. Leave the canonical empty unless the page has a preferred address elsewhere; none is written for a page that has not been given one.

SEO Tools in the Content Manager holds the site-wide values: verification codes for Google, Bing, Yandex and Baidu, the Facebook app id, a global JSON-LD schema block, the sitemap wizard, and a Default share image — the picture a shared link carries when its page has none of its own; about 1200 by 630 pixels works everywhere.

sitemap.xml lists each published page once (a translation shares its original's address), leaves out templates and every page set to Do not index this page — the home page included — and lists every visible product group, the knowledgebase's public articles, the published updates whose date has come, and the published gallery albums. robots.txt is answered by the product as well. A static robots.txt in the site root is served by the web server ahead of it, which is fine.

Since 1.12.0 that live sitemap is the only one. The sitemap wizard on SEO Tools shows what it lists and adds extra links to it, and writes no file. A sitemap.xml file an earlier wizard wrote, which the web server served instead of the live sitemap, is put aside once as sitemap.xml.replaced-<date>; a file the site placed itself is named on SEO Tools, so it can be removed. The business details SEO Tools gives search engines come from the Business profile.

Check Search Visibility after upgrading to 1.11.0.

Before 1.11.0 every page but the home page told search engines "noindex, nofollow", whatever its Search Visibility setting said, because a page reached by its own address inherited the mark of the router's not-found answer. 1.11.0 corrects this, so each page's own setting now decides. Review pages you do not want indexed.

Page workflow

  1. Create a page and define its language, URL, title, and search metadata.
  2. Add sections in narrative order: promise, proof, workflow, detail, FAQ, and action.
  3. Choose assets from the media library and write accurate alternative text.
  4. Use the page's Custom CSS and Custom JavaScript panels for scoped enhancement.
  5. Preview desktop, tablet, mobile, light mode, and dark mode.
  6. Save as a draft while the page is being built, then set it to Published (or schedule it), test the public URL, and verify menu and sitemap placement.

Friendly Page URLs

When Friendly Page URLs is enabled, WBAMS publishes extensionless root and nested CMS paths while preserving each stored .php URL as a compatible route. An extensionless path first gives a declared add-on the opportunity to claim it. If no add-on claims the validated path, WBAMS forwards it to the CMS with a server-only marker; the CMS resolves that marker only while Friendly Page URLs remains enabled.

This boundary prevents a clean-looking unknown path from becoming a homepage or an accidental CMS route. Claimed add-on routes retain priority, native Updates and Knowledgebase routes retain their own loaders, Contact remains connected to contact.php, and an unknown route—or a clean CMS route while Friendly Page URLs is disabled—must remain 404.

Since 1.11.0, on a site with friendly URLs, a page asked for in the basic form (index.php?rp=/updates) answers GET and HEAD requests with a permanent redirect to its clean address, so every page has one address. A section button that links to a WBAMS page works in either URL style, and can name the page the way the menus do, such as @module:knowledgebase. On a site with basic URLs, the home page's canonical address is the site's address, not …/index.php.

Routing regression matrix

Test /about-us and its trailing-slash form; /legal/privacy-policy and /legal/terms-of-use with and without trailing slashes; every stored .php equivalent; native /updates… and /knowledgebase… paths; /contact; one claimed add-on route; one unknown route; and one clean CMS route after Friendly Page URLs is disabled.

Page and mega-menu setting integrity

CMS page-builder, menu, and mega-menu properties use one setting row for each (relid, setting) pair. WBAMS writes these values with an atomic upsert, and the database enforces that relationship with named unique indexes on cms_page_settings and cms_mega_menu_settings. The separate cms_menus table is a legacy store and may correctly be empty. Since 1.10.0 the website's menus are built in Content Manager › Menus, which keeps them in a table of its own; the older header, footer and mega-menu records are what the builder copies from, once, the first time it is opened.

The WBAMS 1.1.1 updater repairs older data before adding the constraints. For each duplicate pair it keeps the highest-ID row and therefore its latest stored value, removes older rows, and then adds the exact unique key if an equivalent one is not already present. The migration is repeatable and conditionally skips a table that is absent.

Back up before cleanup

The duplicate collapse is intentional and not reversible without a database backup. After updating, verify that page, header, footer, and mega-menu counts reflect real records; confirm both unique indexes; edit and save representative items twice; and verify that each setting still has exactly one row.

Custom code

Scope styles beneath a page-specific class. Write progressive JavaScript that leaves content usable when scripts fail. Avoid inline secrets, remote code, global selectors, and behavior that changes billing or authentication.

.wbams-page-platform .capability-card {
  container-type: inline-size;
}

document.querySelectorAll('.wbams-page-platform [data-reveal]')
  .forEach((element) => observer.observe(element));
Synchronization

Serepok reads CMS settings for logos, menus, footer content, theme mode, contact information, payment icons, and public-page presentation. Change these through CMS settings so every page stays consistent.