Customizing Pages

Give any page a template of your own - a new design from scratch, or a safe copy of a shipped one - without editing a single theme file, so everything you build survives updates.

Introduction#

Every page body in Hadrian lives under core/pages/, and the Page Manager renders whichever template you activate. That structure is the whole customization story: to change what a page renders, you add files beside the shipped ones and pick yours - you never edit theirs.

This page is written for whoever edits the files - a developer comfortable with Smarty. If that is not you, the takeaway is that a customized page installs by upload, activates from the Pages screen like anything else, and can be switched away from at any time.

Before you touch a file#

Most customization needs no files at all. Cheaper routes, in the order worth trying:

Files come in when the markup of one page has to change.

Add a template to a page#

Any page can offer more than one template - not just the three that ship with alternatives. A template is one folder:

templates/hadrian/core/pages/<page>/<name>/
    <name>.tpl     the markup (required)
    <name>.php     name + description for the admin card (recommended)

1. 1Pick the page's folder under templates/hadrian/core/pages/ - for the Affiliates page, core/pages/affiliates/.
2. 2Create a folder for your template inside it. Lowercase letters, digits and hyphens only - affiliates/wide/.
3. 3Copy the body of the shipped template as your starting point: default/default.tpl in the same page folder. Save your copy as wide/wide.tpl.
4. 4Add wide/wide.php so the admin card has a name and a description.
5. 5Make your changes to wide/wide.tpl.
6. 6Open Hadrian -> Pages, click the page - your template is already a card. Activate it and save.

The metadata file is three lines:

<?php
return [
    'name'        => 'Wide',
    'description' => 'The affiliates page with the stats row across the full content width.',
    'fullPage'    => false,
];

There is no cache to clear and no registration step - templates are discovered live from the filesystem, so the card appears on the next load of the editor.

Modify an existing template#

To change a shipped template's markup, do not edit it - duplicate it and edit the copy. The original stays untouched for updates to replace, and you can switch between the two from the admin at any time.

1. 1Duplicate the template's folder - core/pages/clientareahome/bento/ to core/pages/clientareahome/bento-mine/.
2. 2Rename the files inside to match the new folder: bento-mine.tpl, bento-mine.php.
3. 3Change the name in bento-mine.php so the two cards are distinguishable.
4. 4Edit bento-mine.tpl.
5. 5Activate your copy in Hadrian -> Pages.

Template settings are stored per template, so your copy starts at its own defaults and the shipped template keeps its configuration - switching back is always safe.

What a template can read#

Your .tpl runs with everything the shipped one had: every WHMCS variable for that page, the theme's language file as $hadrianLang.*, and the per-page state Hadrian resolves for you:

Two conventions from the shipped templates worth copying: link your page's stylesheet from inside the template with the version cache-buster (assets/css/pages/<page>.css?v={$hadrian.version}), and declare a supportedOptions block in your template's .php if you want settings of your own to appear in the editor - the shipped Dashboard templates are working examples of every option type.

Replace a page outright#

When you want a page's body entirely yours - no card, no choice - drop one file:

templates/hadrian/core/pages/<page>/overwrites/overwrites.tpl

While that file exists it renders instead of every template for the page, including whichever card is active in the admin. Deleting it hands the page back. The full mechanics, and the one warning that matters - the admin keeps showing a card as Active while your file is what renders - are in Page Manager.

Two smaller override points#

Beyond page bodies, the theme checks two specific paths before rendering its own partials:

These are the only two. In particular there is no override point for header.tpl - the head, SEO tags and layout dispatch are managed by the theme, and the supported ways to change what they output are the admin screens.

What survives an update#