Foundra (tpl_foundra) is a Joomla 6 site template built for Solidshop.
It ships its own layouts for every Solidshop storefront view — product pages,
listings, cart, checkout, the customer account — for the storefront modules
(mini-cart, product strips, slideshow, category tiles, brands, reviews, recently
viewed), and for the Joomla views a shop leans on: articles, a category blog, the
Contact page and the sign-in, registration and password-reset screens. Five presets,
your own primary and accent colours, four header layouts, header and footer colours, a
choice of fonts served from your own site, and a dark mode you can leave to the
visitor’s system, force, or hand them as a toggle.
This page is the setup reference. See the Foundra extension page for the feature overview, and demo.solidshop.app for the template running on a full demo store — every block on that site is a module placed in one of the positions listed below.
Requirements
- Joomla 6.0 or later
- PHP 8.4 or later
- Solidshop 1.7.0 or later — install Solidshop first; the template’s installer refuses to run against an older core. Foundra 1.1.0 draws the colour and image swatches and the specification rows that arrive in Solidshop 1.7.0 (Foundra 1.0.1 ran on 1.6.0, Foundra 1.0.0 on 1.5.0). Foundra 1.2.0 runs on 1.7.0 too; the Look screen that edits its options beside a live preview arrives with Solidshop 1.8.0
Installation
After purchase, the template package is available from the downloads area of your account on solidshop.app. Your purchase includes 12 months of updates and support.
In your Joomla admin, go to System → Install → Extensions and upload the zip. Joomla installs the template, its media (stylesheets, script, the four bundled fonts) and the language files for all 23 locales.
Go to System → Site Template Styles and click the star next to Foundra - Default. Every page now renders through Foundra. To try it on a few pages first, open the style instead and assign it to selected menu items on its Menu Assignment tab.
A fresh template shows an empty header until modules are assigned to its
positions: your main menu in nav, and the product search, an
account link and the mini-cart in header. See
Module positions for the full map and a
landing-page layout that works.
Template options
Open the style under System → Site Template Styles → Foundra - Default. The settings are grouped in tabs: Brand, Style, Header, Footer, Shop, Features and Custom Code; the last is covered in the next section. On Solidshop 1.8.0 and later the same tabs are in Solidshop’s own Look screen, beside a preview of the home page, for whoever may change Solidshop’s options. A setting marked Preset default keeps whatever the chosen preset does; pick a value and it holds on every preset.
Brand
| Setting | Default | What it does |
|---|---|---|
| Logo Type | Image | Image shows the logo files below; Text shows a wordmark instead. |
| Logo (Light Mode) | — | The header logo. SVG recommended. With no logo set, the header shows the site name as text. |
| Logo (Dark Mode) | — | An alternative file shown whenever the page is in its dark scheme — from the visitor’s system, the store’s Dark only setting, or the toggle — and on a coloured or dark header and footer, and on the transparent header while it lies over the hero. Leave empty to use the main logo everywhere. |
| Logo Text | — | The wordmark for the Text logo type. Empty uses the site name. |
| Favicon | — | Browser tab icon (ICO, PNG or SVG). Empty uses the template’s own. |
Style
| Setting | Default | What it does |
|---|---|---|
| Store Preset | Default | The overall look: Default, Boutique, Electronics, Marketplace or Minimal. Only the active preset’s stylesheet is loaded. See Presets. |
| Primary Color | #2563eb |
Buttons, links and interactive elements. Left at its default, the active preset’s own colour is used; once changed, your colour replaces it on every preset, and the lighter and darker tints Foundra derives from it follow. Text stays readable whatever you pick: buttons on a light colour get dark labels, and links and other text in your colour take a deeper shade of it where the colour itself would be too pale to read. |
| Accent Color | #f59e0b |
Badges, sale prices and callouts. Left at its default, the preset’s own accent is used; once changed, it applies on every preset, with its lighter and darker tints. |
| Page Background | Preset default | The colour behind the page. Soft grey is a light grey the white cards lift off; Warm an off-white; Tinted mixes a little of the primary colour into white, so it follows the colour you chose. Dark mode uses a dark shade of the same choice. |
| Corners | Preset default | The corners of cards, inputs and buttons. Sharp squares them; Softly rounded rounds them a little; Round rounds cards further and makes the buttons pills. |
| Heading Font, Body Font | Preset default, System Default | Each list has two groups. On the visitor’s device — System Default, Sans-serif, Serif — loads nothing, though each device shows the first font of the stack it has, except Foundra’s own Inter on a device that has none of the stack’s fonts. Included with Foundra — Inter, Manrope, EB Garamond and, for headings, Noto Serif Display — looks the same everywhere and is served from your own site, one small file per face on most pages, never from a third party. The faces carry the Latin, Vietnamese, Cyrillic and Greek letters; other scripts keep the device’s fonts. Preset default keeps the preset’s heading font (Boutique’s serif). |
| Container Max Width | 1320px | Maximum width of the content area: 1140, 1320 or 1536 px. |
| Container Layout | Static | Static keeps content within the container width; Fluid stretches it to the full viewport. |
Header
| Setting | Default | What it does |
|---|---|---|
| Header Layout | Logo on the left, menu beside it | How the logo, the menu and the search, cart and account controls are
arranged on wide screens. Logo in the middle, menu below and
Large logo above the menu give the menu a row of its own;
Menu split either side of the logo is the boutique header, with the
controls on a strip above. On phones every layout is the same bar with the
menu in a drawer. The split layout halves the top-level items of the Joomla
Menu module in nav, the first half before the logo; a menu from
another kind of module, or with another layout, stays one list. |
| Header Position | Above the page | Transparent over the first block lays the header over whatever
comes first on the page — meant for a full-width hero in the
fullwidth position — and turns solid once the visitor
scrolls. |
| Header Colour | Plain | The header’s background and text: the page’s own surface, the
primary colour, or a dark bar. The bar under the header (the
top position) takes the same colour; dropdown panels keep the
page’s surface. |
| Pin the Header | Yes | Keep the header at the top of the window while the page scrolls. |
Footer
| Setting | Default | What it does |
|---|---|---|
| Footer Layout | Columns | Columns puts the footer-1 to footer-4
positions side by side. Centered opens with the logo and lays the
modules out in one centered column, with menus and plain lists as a row of
links. |
| Footer Colour | Dark | The footer’s background and text: a dark block, the page’s own surface, or the primary colour. The bottom strip takes the same colour. |
Shop
| Setting | Default | What it does |
|---|---|---|
| Products Per Row | 4 | Product cards per row on listings at desktop width (2, 3 or 4); narrower screens drop columns on their own. Left at its default, the preset decides (Minimal uses 2, the others 4). |
| Product Card Style | Standard | Standard is a bordered card with the details under the picture. Overlay uses a portrait picture with the name and price laid over its lower edge on a dark gradient. Minimal drops the border and shadow so the pictures sit on the page. |
| Product Picture Ratio | Preset default | The shape of the picture on product cards: Square, Portrait or Landscape. Left at the default the preset decides: square for Default and Electronics, portrait for Boutique and Minimal, landscape for Marketplace. |
Features
| Setting | Default | What it does |
|---|---|---|
| Dark Mode | Auto (follow system) | Auto follows the visitor’s system setting. Light only and Dark only force one scheme for everyone. User toggle follows the system until the visitor clicks the sun / moon button Foundra adds to the header; their choice is remembered in their browser. |
| Show Back to Top | Yes | A floating button that appears once the visitor has scrolled down. |
Updating from Foundra 1.1.0 or earlier. The old Header Style became Header Layout and Header Position, and Font Family became Body Font; the update moves a style’s saved values across, so the header and the font a store had are the ones it keeps.
Custom code
The Custom Code tab has five slots. Everything you put there survives a template update, because it lives in the style’s settings, not in the template’s files.
| Slot | Where it lands |
|---|---|
| Custom CSS | A stylesheet in the page head after every other stylesheet, the
modules’ included, so your rules win — the place to override a
colour token or tweak a spacing (see Customising).
Every page carries classes for the component, view, menu item and page class
(view-product, itemid-101), so a rule can target one
page. |
| Custom JavaScript | An inline script in the page head, after the template script. |
| Custom Head Code | Raw HTML before </head> — verification meta tags,
analytics snippets. |
| Custom Body Start Code | Raw HTML right after <body> — a tag manager’s
noscript block. |
| Custom Body End Code | Raw HTML before </body> — chat widgets, deferred
scripts. |
Custom CSS is a code editor with CSS highlighting; it takes CSS only, so
@import rules are removed — to use a font or image of your own,
upload it to Media and refer to its address. It is printed on every page type, the
error, offline and popup pages included. The three raw HTML slots —
Custom Head Code, Custom Body Start Code and Custom Body End
Code — are also rendered on the template’s error page, so an
analytics snippet reports the broken links visitors land on. Custom
JavaScript applies to regular pages only.
For larger customisations, Foundra also loads two files automatically when they
exist: templates/foundra/css/custom.css and
templates/foundra/js/custom.js (a non-empty .min variant
beside either is preferred). Nothing in the template references these files
otherwise, so an update never overwrites them — but they sit inside the
template folder, so back them up before uninstalling.
Presets
A preset is a stylesheet that restyles the template’s design tokens — palette, corner radius, shadows, spacing, the product card’s picture ratio. Switching presets changes no content and moves no modules.
| Preset | Character |
|---|---|
| Default | Blue and amber, comfortable radius, soft shadows, square product pictures that lift on hover. The safe choice for a general catalogue. |
| Boutique | Serif headings, a purple and gold palette, portrait 3 : 4 product pictures, generous whitespace. Apparel, jewellery, homeware. |
| Electronics | A dense four-column grid of square, bordered cards; sky blue and orange; tight radius. Built for comparing specifications at a glance. |
| Marketplace | Green and amber, rounded cards and pill buttons, a filter sidebar with more presence. Broad catalogues with many brands. |
| Minimal | Monochrome, no radius, no shadows, two large product pictures per row and the most whitespace of the five. Few products, big photography. |
Presets bring their own colours, until you set yours. Each preset ships a palette, and the Primary and Accent Colour options show the Default preset’s blue and amber. Leave them there and the preset you chose keeps its own colours; change either one and it applies on every preset. In dark mode Foundra always uses its own lighter palette for contrast — see Customising to set a dark-mode colour of your own.
Module positions
Foundra defines nineteen positions. Each renders only when it has a published module, so an unused position costs nothing and leaves no gap.
| Position | Where | Typical use |
|---|---|---|
banner |
Above the header, full width | A site-wide notice |
nav |
Header, and the mobile menu drawer | Your main menu — one module serves both |
header |
Header, end side | Product search, an account link, the mini-cart; the dark-mode toggle joins them when enabled |
top |
A bar under the header | An announcement bar (free shipping threshold, a sale) |
breadcrumb |
Under the top bar | Joomla’s Breadcrumbs module — Foundra overrides its layout |
fullwidth |
Top of the main area, edge to edge | The slideshow / hero, so the picture meets the header |
main-top |
Main area, above the content and sidebars | Landing-page blocks: a USP strip, category tiles, a featured strip |
sidebar-left, sidebar-right |
Beside the content | The filters module on listing pages. Either sidebar switches the page to a sidebar layout; both give three columns |
content-top, content-bottom |
Inside the content column, around the component | Blocks that belong to the page’s own content |
main-bottom |
Main area, below the content and sidebars | More strips: new arrivals, deals, best sellers, brands, reviews, the blog teaser, a newsletter form; “You may also like” and “Recently viewed” under product pages |
footer-fullwidth |
Between the main area and the footer, edge to edge | A call-to-action band |
footer-1 … footer-4 |
The footer, up to four equal columns | About the store, a shop menu, a customer-service menu, contact details and the currency switcher. Only the columns with a module render |
footer-bottom |
Under the footer | Copyright line, payment-method logos, legal links |
debug |
End of the page | Joomla’s debug output |
A landing page needs no article and no page builder: create a
Storefront home menu item (the component prints nothing on it), then stack
modules in fullwidth, main-top and
main-bottom in the order above. Every block on the demo site is one of
the storefront modules or a Joomla Custom
module carrying a short piece of HTML. When the slideshow is the first thing on the
front page, set its Heading level to H1 and leave the menu item’s page
heading off, so the page keeps a single H1.
Slideshow layouts
The Slideshow module’s Layout option (on its Advanced tab) lists three layouts of Foundra’s own beside the default full-bleed hero. All three keep the module’s controls, keyboard operation and reduced-motion behaviour; they change only how a slide is drawn.
- Split — the picture on one half and the text on a plain surface on the other, with no scrim; the picture keeps a 4:3 box, so nothing moves as it loads, and the two stack picture-first on a phone.
- Centered — the full-bleed photo with the text centred in a narrower measure, the dots under it and the arrows on either side.
- Banner — a slim strip with the eyebrow, heading and button on one line, for a promotion above a listing or on a category page; one slide is a static band, several a small slideshow. With a picture it is a scrimmed photo, without one a plain surface.
Categories layouts
The Categories module’s Layout option lists three layouts of Foundra’s own beside the default picture tiles. All three keep the module’s display options — picture, name, product count, heading level, columns — and the whole tile stays one link; they change only how a tile is drawn.
- Editorial — the first category as a large feature tile, two columns wide and two rows tall, with the rest beside and below it; on a phone every tile is the same size again. Put the category you most want seen first.
- Compact — a row of small round-cornered thumbnails with the name beneath and no scrim, sized for a sidebar or a thin band; Columns is the count across, and with the picture off the tiles become a row of chips.
- Cards — the picture on top in a fixed box and the name and count on a bordered panel below, like the product card; for light or busy category pictures, where a label laid over the picture reads badly.
Menu chips
Joomla’s Menu module gains a Chips layout: one row of pill links for a
blog’s topics or a catalogue’s sections, with the current page filled in.
For a blog organised by tags, give the Blog menu item one Tagged Items child
per tag, then publish a Menu module in content-top with:
- Menu — the menu that holds the Blog item.
- Base Item — the Blog item; Start Level and End Level — 2, the level of its children.
- Layout (Advanced tab) — Chips.
- Menu Assignment — the Blog item and its tag items.
The Blog page itself leads the row as All, so every tag page links back to the full list. The module title names the navigation for screen readers, so call it what the row is (“Blog topics”) even with the title hidden. The row wraps on a phone rather than scrolling, so no topic is hidden off-screen.
Smart Search
The Smart Search module and the search results page use Foundra’s form
controls, cards and colour tokens, including the suggestion list under the box.
In a sidebar the search button shows only its icon. A page of results is served
noindex, follow, so search engines follow the links to your pages but
do not index the result list; a Robots value set on the search menu item
takes precedence.
To search one part of the site only — your documentation, say — create a Smart Search Search Filter for that category, a Search menu item that uses it, and set the module’s Search Filter and Set ItemID to the same pair. Publish the module at the top of the sidebar that lists those pages.
What Foundra overrides
Foundra does not restyle Solidshop’s default markup from the outside; it replaces the templates. That is what lets it drop the Bootstrap grid on its own pages and use one card, one spacing scale and one set of colour tokens throughout.
- Solidshop views — product page (including the layouts the Downloadable and Service add-ons register), product listing, cart, checkout and its confirmation, order tracking, wishlist, and every customer account page: overview, orders, order detail, addresses, profile, wishlist, invoices, downloads, bookings, reviews and subscriptions. Where an add-on is not installed, its account page shows a short notice with a link to the add-on instead of an empty table.
- Solidshop layouts — the product card, media gallery, name, price, options, variants, quantity and share / wishlist controls; the mini-cart drawer; checkout and account address forms; the account sidebar; the coupon form; promotion notices; the invoice view.
- Storefront modules — mini-cart, products, slideshow, categories, brands, recently viewed, reviews and the language switcher.
- Joomla views — a single article and the category blog
(
com_content), a tag’s list of tagged items (com_tags), the Contact page (com_contact), sign-in, registration, password reset and reminder, and the profile (com_users), the Smart Search page and module (com_finder), the Articles module, the Menu module (its default layout, which the split header uses, and Chips), Breadcrumbs, pagination, and the shared article layouts for images, read-more, tags and the info line. The blog page, a tag page and the “From the blog” module render the same card, so the three never look like different sites. - Error and offline pages — the error page keeps the template’s header and logo; the offline page is a single card with your logo, the offline message and the sign-in form, on the same colour tokens.
Foundra still loads Bootstrap, because Joomla’s own extensions, the storefront add-ons and many third-party extensions render Bootstrap classes, and re-skins that chrome onto its own tokens. Joomla ships only the left-to-right build of Bootstrap, so on a right-to-left site Foundra loads Bootstrap’s right-to-left build of the same version in its place. The forms, buttons and tables those extensions print then mirror along with Foundra’s own pages, with nothing to configure.
Dark mode, RTL and accessibility
- Dark mode is a second set of colour tokens, so every override and every module follows it. Brand artwork in the brand strip deliberately stays on a light plate, since most logos are dark ink on transparency.
- Right-to-left layouts mirror through logical CSS properties — margins, padding, borders and positioning flip with the text direction, and the arrow controls of the slideshow and product gallery mirror with them. Markup from other extensions mirrors through Bootstrap’s right-to-left build, described above. Persian, Arabic and Hebrew are among the bundled locales.
- Accessibility: skip links to the content and the search, labelled landmarks, a mobile menu that traps focus while open and closes on Escape, visible focus states, and animation that stands down for visitors who ask for reduced motion.
Customising
Foundra is inheritable. Under
System → Site Templates, open Foundra and click
Create Child Template; then make the child the default style. A child
carries only the files you add to it — a copied html/ override, a
replacement index.php — and reads everything else from Foundra, so
a template update leaves your files untouched. Override a Solidshop view by copying
it from templates/foundra/html/com_solidshop/ into the same path inside
the child.
For colours and spacing, no file is needed. The compiled stylesheet reads its values
from --foundra-* custom properties, so Custom CSS with a handful
of token overrides restyles the whole site at once: the buttons’ corners are
--foundra-radius-button, the product card’s picture
--foundra-card-ratio. Presets and the style’s options set their
tokens on the page’s body, so an override names
body.foundra. The header’s and footer’s colours are
--foundra-header-* and --foundra-footer-* tokens set on the
header and footer themselves, so re-point them there. A dark-mode value names the
dark-mode class Foundra puts on the root element.
body.foundra {
--foundra-radius-md: 0.25rem;
--foundra-space-10: 5rem;
}
.foundra .foundra__header {
--foundra-header-bg: #0f172a;
}
:root.dark-mode body.foundra {
--foundra-primary: #2dd4bf;
}
Updates
Foundra registers with Joomla’s update system. When a new version is published,
it appears under System → Update → Extensions like any
other extension; updating replaces the template’s own files and media and keeps
your style settings, custom code slots, custom.css / custom.js
and any child template.
Uninstalling
Joomla will not uninstall the default site template, so first star another style
(Cassiopeia, say) under System → Site Template Styles, and
remove any child template of Foundra. Then uninstall Foundra from
System → Manage → Extensions. The template folder goes with
it, including custom.css and custom.js if you created them
— copy them out first. Solidshop, its modules and your store data are not
affected; the storefront simply renders through the other template.