Brock Theme¶
Brock is a conversion-focused storefront theme. It is built on top of Nova (Brock → Nova template fallback), so every page works from the moment a site switches to it; Brock replaces the pages where the design most affects whether a shopper buys.
Site admins pick it under Admin → Settings → Theme (Choosing a Theme); platform staff can also set it per site in System → Tenants → {site} → Theme (theme name Brock). A site's Design Brief (brand colour, font, corner radius, image shape) applies to Brock exactly as it does to Nova.
Design principles¶
| Principle | What it means on the page |
|---|---|
| One colour means "buy" | The brand colour (--color-primary) is used only on the purchase path: Add to basket, Checkout securely, Pay. Navigation, secondary buttons, selected size/colour, badges and links are ink on white, so the next step is always the one thing that stands out. |
| Search is a field, not an icon | A full-width search box is in the header on every screen size (with as-you-type suggestions). On phones it tucks away while scrolling down and returns on scroll up. |
| Promises stated plainly | Delivery, returns and "secure checkout" appear in the header strip, beside Add to basket, in the basket summary and above the footer — the same words everywhere. Nothing is claimed until the site sets it. |
| Even product grids | Product images sit on a neutral tile (packshots and lifestyle photos line up), with the saving shown as a percentage and the was-price. |
| Enclosed checkout | Checkout pages drop the menu, search and promo strip: logo, a way back to the basket, and "Secure checkout". |
What Brock redesigns¶
| Area | Highlights |
|---|---|
| Header / footer | Announcement bar, promise strip, search-first header, mega menu (collection menu and admin-built menu), slide-in mobile menu, basket button showing item count and running subtotal, reassurance row, payment marks. A long site name wraps to two lines (then ends in an ellipsis) beside the logo, so it never runs into the search box or the account and basket buttons. No per-site CSS is needed. |
| Listings | Collection, search and merchandising pages: sticky count + sort bar, sub-category chips, filter rail (desktop) / slide-in filter panel (mobile), applied-filter chips with Clear all, 2/3/4-column grid, pagination with "Showing 1–24 of 312". The rail opens with the category nav (parent, sub-categories with counts, or a leaf's siblings; the Category group on search), shows the groups the results chose with the rest under More filters, and has price buckets plus min/max inputs; colour filters show a swatch dot before each value and number filters (a length) get range buckets plus the same min/max inputs with their unit in place of £; with JS each pair of inputs gets a two-thumb slider. In the phone panel taps stage filters and Show N products applies them all with a live count (nova/js/modules/facet-sheet.js); closing it discards them. On phones the way into the panel is a sideways-scrolling quick-filter bar above the results: Filters (n), a pill per top group that opens the panel at it, and one-tap In stock / On sale (shared fragment/quick-filters). A category page has a Search in {category} box under its heading. When the searched term has a search rule with a banner, it shows under the heading, above the results (shared fragment/search-banner, styled by bdgr.css in the theme's accent). |
| Product page | Gallery beside a buy box that stays in view on desktop; brand, title, rating, price with saving, size/colour buttons, honest stock line ("Only 3 left" at ≤5), quantity + Add to basket, promises, collapsible Description and Delivery & returns; a docked buy bar on phones. |
| Mini basket | Clicking the header basket opens the whole basket in a drawer from the right (full width on phones): "Your basket" with the item count, every line with its picture, options, a quantity stepper and Remove, stock notes, and the subtotal with Checkout securely and View full basket pinned to the foot. Changes are made in place, with no page load, and the header count and subtotal follow. Prices still being re-worked after a change show a shimmer until they're ready. Without JavaScript, and on the basket and checkout pages, the button simply goes to the basket page. |
| "Added to basket" | Adding opens a compact confirmation, deliberately unlike the mini basket so nobody mistakes it for the whole basket: on desktop a small pop-over hanging from the header basket (green notch and top rule, light scrim), a short bottom sheet on phones. It shows the item just added, then "Plus n other items in your basket", the basket subtotal and item count, Checkout securely and View basket (n). "Plus n other items" opens the mini basket with the new line highlighted; View basket (n) goes straight to the basket page. |
| Basket | Line items with stepper, save for later and remove; order summary with "Delivery: calculated at checkout" until chosen; one Checkout securely button, which is also pinned to the bottom of the screen on phones (with the total) until the summary's own button is in view. See Basket Page. |
| Checkout | Both modes: the stepped checkout (numbered step cards — details, address, delivery, payment — each collapsing to a recap with Change) and the single-page checkout (unifiedCheckout extension, restyled in place). Email is asked first; address fields have plain labels and specific errors; the order summary folds to one line on phones. |
| Order confirmation | Tick, thanks, order number and the email the confirmation went to, then the order, totals, contact, addresses and payment. |
| Rails | Trending, featured and recently-viewed products use the same card as listings, swipeable on phones. |
Everything else (account pages, blog, content extensions) renders Nova's template inside Brock's header and footer, using Brock's colour tokens.
Configuring the copy¶
All Brock wording is in messages.properties under brock.* and can be overridden per site in
Admin → Settings → Site text (/admin/shopSettings/text). The ones a merchant should set:
| Key | Default | Where it shows |
|---|---|---|
brock.promise.delivery |
(empty) | Header strip, product page, basket, footer. e.g. "Free delivery on orders over £50" |
brock.promise.returns |
(empty) | As above. e.g. "Free 30-day returns" |
brock.promise.secure |
Secure checkout | Header strip, product page, footer |
brock.promise.help |
(empty) | Footer reassurance row. e.g. "Questions? We reply within one working day" |
brock.pdp.deliveryInfo |
(empty) | "Delivery & returns" section on every product page (HTML allowed) |
brock.pdp.priceNote |
(empty) | Line under the product price, e.g. "Including VAT" |
brock.confirm.next |
(empty) | Under the order number on the confirmation page |
nav.banner.message |
(empty) | Dark announcement bar above everything. Set it in Admin → Settings → Storefront → Announcement (storefront-announcement; switch the band off with Show Announcement Band); the Site Text key is the fallback when that is empty. |
The header strip only appears once delivery or returns is set, so a new site never shows a promise it hasn't made.
Sites without search: one header row¶
With search off (useSearch, or no search engine set up) there's no search box for the header's
middle, so the menu moves up into the bar: logo, menu, then the header link and button on the
right, all on one row. A site with search keeps the menu on its own row under the search bar.
The Header Link and Header Button settings (Admin → Settings → Storefront,
storefront-header-link-label / -url and storefront-header-cta-label / -url) add a text link
(e.g. Sign in) and a button (e.g. Start a free trial) to the bar on any Brock site. On phones the
link moves into the slide-in menu. The button stays in the bar on a site that sells nothing. On a
shop, where the account and basket buttons need the room, it moves into the menu too.
When a long menu doesn't fit beside the logo and buttons (on a narrow laptop, say), the header uses the phone layout instead: the menu button and the slide-in menu. It goes back to one row once the window is wide enough. Without JavaScript the menu scrolls sideways instead.
Sites that sell nothing¶
For a corporate or brochure site, turn off the site config key
storefront-commerce-chrome-enabled (category storefront-config, in the admin's site
configuration or through the MCP manageSiteConfig tool). The header then drops the Sign in / account and Basket buttons (and
the mobile menu's account and basket links), and the footer drops the payment marks. It defaults to
on and applies to every theme (Nova, Brock, Bistro, Depot, Pop, Atelier, Spec, Ridge and Diorama). StorefrontChromeInterceptor reads the key and puts the
commerceChromeEnabled boolean on every page model; the templates only consume it. Hiding the site
name beside a logo is a separate option (hideSiteNameInNav).
With the account link gone, staff would have no way back to the admin, so every theme shows anyone
signed in with an admin role an Admin button floating in the bottom-right corner. It shows on
every site, whether or not this switch is off. It opens links to Site Administration, Edit this page (the page with ?inlineEdit: the side panel
editor with a live preview, see Content Management; Stop editing this page
once there, which replaced the themes' old Exit Edit Mode pill), My Account, the basket and
Sign out. While a page is being edited the button starts in the bottom-left corner, clear of the
editor's side panel. Beside it, one small button moves it to the next corner and the other hides it; both
last until the page is reloaded, nothing is remembered. StorefrontChromeInterceptor puts an
AdminDock on the page model as adminDock; every theme's footer includes
nova/fragment/admin-dock.html beside the preview badge, and modules/admin-dock.js adds the move
and hide buttons (the menu itself is a <details> and works without JavaScript).
The same switch changes the search box's accessible (screen-reader) label from "Search products" to
"Search this site", so a consultancy using content search isn't described as a shop. The wording
comes from the search.label.products / search.label.site message keys (English and Dutch in the
bundles, so Site Text can override them). The Java side picks the key: SearchBarExtension puts
searchLabelKey on its model and StorefrontChromeInterceptor puts the same attribute on the page
for the header's fallback search form; templates only render it. The placeholder is unchanged, so
the searchBar extension's configurable placeholder still wins.
The "Shop all" link in menu dropdowns¶
A menu item with a dropdown is a single button, its name and chevron together: hovering or clicking
it opens the dropdown (in the mobile drawer, tapping it opens the accordion). Each dropdown ends with
a link to the menu item's own page, "Shop all Services" by default. In the mobile drawer it is a plain link at the top of the
accordion, or after the other links if you set nav-all-link-position to last (below). If one of the item's own dropdown entries already links to that page (an "All services" entry
you added yourself), that entry is used instead and the automatic link is left out. On a site that isn't a shop (say a consultancy whose menu items are pages),
change or hide it in Admin → Site Configuration, category menu-config, or with the MCP
manageSiteConfig tool:
| Key | Default | Effect |
|---|---|---|
nav-mega-menu-view-all-label |
(empty) | The link text. {0} is replaced with the menu item's name: View all {0} gives "View all Services". Text without {0} is used as-is (View all). Empty uses the theme's wording, the brock.nav.shopAll message ("Shop all {0}"), which Site Text can also change. Plain text, so apostrophes need no escaping. |
nav-all-link-position |
first |
Where the link sits in the mobile menu's accordion: first (top of the list) or last (after the other links). It is a plain link either way, and the desktop dropdowns keep it at the foot. Also applies to Bistro and Ridge, where the link reads "All {0}". |
nav-mega-menu-view-all-enabled |
true |
false hides the link. The item's name opens its dropdown, so its own page is then not linked from the menu: add it to the dropdown as a child item if it should be. |
On a site that sells nothing (storefront-commerce-chrome-enabled off, see above) an empty label
gives "View all {0}" rather than "Shop all {0}". A label you set still wins, and
nav-mega-menu-view-all-enabled = false still hides the link.
The same keys drive Pop, Depot, Spec and Atelier (each with its own <theme>.nav.shopAll default)
and Nova (default "View All {0}" and "All {0}", the nav.megaMenu.* messages). On
Nova, turning the link off hides the mega-panel "View All" links but keeps a plain
dropdown's "All {0}" link, as that dropdown's parent opens the menu rather than its page.
The collection menu (collectionChooser) still says "Shop all": it only ever lists product
collections.
A change takes effect on the next page view: the setting is part of the menu hash, so browsers
holding a cached copy of the menu fetch it again. (Site Text changes are not, so a changed
brock.nav.shopAll message reaches returning visitors once the menu is edited or the platform is
upgraded.)
Breadcrumbs on content pages¶
Content pages get a breadcrumb under the header (and above any hero), built from the main menu,
for example Home / Services / Legacy modernisation. It uses the same markup and styling as the
collection and product breadcrumb, a little tighter. It is hidden on the home page, basket,
checkout, account and error pages, and per site with cms-page-breadcrumbs-enabled. The same
applies to Pop, Depot, Spec and Atelier. See
Content Management for how the trail is built.
For developers¶
- Templates:
web-mvc/src/main/resources/templates/brock/. Styles and behaviour:resources/settBuilder/themes/brock/css/brock.cssandjs/brock.js, linked from Brock'sfragment/head.htmlafter Nova'sbdgr.css(and before the Design Brief'stheme.css). - Brock's
ThemeContextpointscssPath/jsPath/imagePathat Nova's folders so Nova templates and extension scripts keep working; see Theme Resolution. - Brock reuses Nova's scripts (variant picker, sticky buy bar, search suggestions, basket repricing, checkout) unchanged; each Brock template documents the ids and classes it keeps for them at the top of the file.
- The mini basket is
fragment/mini-basket :: mini-basket-panel, rendered in the header from the display order every page already has. Quantity changes post to/basket/update, removals to/basket/removeand clearing to/basket/clear(BasketController). The sharednova/js/ui-components.js(which also runs the category menu and the drawer) sends them throughNovaUi.fragments, asking for two fragments, the drawer's content (mini-basket-content) and the header basket (header-basket), and swaps them in (see Storefront Fragments). Add to basket does the same through the sharednova/js/add-to-basket.js(NovaUi.addToBasket), posting the add-to-basket form to/basketand then opening the "added" pop-over, which reads the count and subtotal from the header basket the server drew. Without script the posts redirect to the basket page. Either way the server is the only thing that draws a basket. - The theme record is added by system update
83.json(idempotent) andinitialisation/templates.json. - Bistro is layered on Brock (Bistro → Brock → Nova), with its own header. Brock
leaves two empty hooks for a theme above it:
fragment/themeAssetsin the head (extra stylesheets and scripts) andfragment/footerNoticeat the top of the footer. The "added to your basket" pop-over is its own fragment (fragment/added-basket) so that header can include it. The product page offers Choose options in place of quantity and Add to basket for a restaurant dish with choices (menuItemUrl).