Themes

A theme changes how the public site and the client area look. PNLCS ships 16 (Setup → Appearance); you can install your own.

What a theme is

A folder under themes/, named by its slug:

themes/
└── acme/
    ├── theme.json        required
    ├── screenshot.svg    shown on the Appearance screen
    ├── views/            optional: Blade views that replace the core ones
    └── assets/           optional: CSS, images, fonts

theme.json

{
    "name": "Acme",
    "slug": "acme",
    "version": "1.0.0",
    "author": "Your Company",
    "description": "Our house style.",
    "screenshot": "screenshot.svg",
    "supports": ["dark-mode", "white-label", "section-builder"],
    "colors": {
        "primary": "#1a4d80",
        "accent": "#337ab7"
    }
}

• slug: lower-case letters, digits, - and _, starting with a letter or digit, at most 50 characters. It is the folder name.
• colors: applied as the active colour set when the theme is activated. Colours you leave out come from the Starter theme, so a theme can set only the few it changes. Look at themes/starter/theme.json for the full list of colour names.

Replacing views

Files in views/ take priority over the core views with the same path. To change the client area's service page, copy resources/views/client/services/show.blade.php to themes/acme/views/client/services/show.blade.php and edit the copy.

Replace as few views as you can: a replaced view no longer receives the improvements and fixes that updates bring to the original. Colours and the homepage sections builder (Setup → Appearance) cover most changes without copying a view.

Assets

Files in assets/ are served at /themes/<slug>/assets/, for example /themes/acme/assets/site.css.

Starting from an existing theme

Every installed theme can be downloaded as a ZIP from Setup → Appearance. Download the closest one, change the slug and name in theme.json, rename the folder to the new slug, and build from there.

Installing

• Copy the folder into themes/ on the server, or
• upload it as a ZIP on Setup → Appearance (the ZIP must contain theme.json; the files may sit inside one top-level folder).

Then activate it on Setup → Appearance. A theme with the slug of a built-in theme cannot be installed over it, and the active theme cannot be deleted.

Keeping your theme through updates

Built-in themes are part of PNLCS and are overwritten by updates; a theme with its own slug is not. Build yours under your own slug rather than editing a built-in one.