AdminStyleRock by bernhard

AdminStyleRock

A message to Russian people

If you currently live in Russia, please read this message.

Easily style your ProcessWire backend with two simple settings:

Or via RockMigrations:

$rm->installModule("AdminStyleRock", [
  'rockprimary' => '#0069B4',
  'logo' => '/site/templates/img/kollar.svg',
]);

Why does this module exist?

1. It provides docs for the rock style
2. It helps developing and maintaining the rock style
3. It might serve as an example how to share your own styles with the community in a modular way instead of sharing admin.less files that can't be updated/monitored by the PW upgrades module.

This means you can submit issues or pull requests to this repository and I can check them easily. Once we have an improved version of the rock style we can as Ryan to pull the changes into the PW Core.

For discussion head over to the support forum thread: https://processwire.com/talk/topic/25668-adminthemeuikit-rock-style/

Also be sure to read the blog post about the new Uikit admin theme customization options that indroduced and explains the foundation for this module.

How does the module work and what does it do?

When installed, the module sets the style property of your $config->AdminThemeUikit array to the rock style that lives inside this repository (not the core version). You could of course simply do that in config.php but the module approach has a benefit: It does also monitor the new file and recompiles automatically whenever something changes. In addition, it also creates a minified version of the admin theme if $config->debug is turned OFF and an unminified version if debug mode is ON.

Wording: THEME vs. STYLE

• THEME: When we talk about a PW admin THEME we mean the stylesheet plus all the PHP files that create the markup and business logic.
• STYLE: A style on the other hand (like the rock or reno style) does only modify the look and feel via changing LESS variables or overwriting CSS

How AdminThemeUikit styles work

AdminThemeUikit uses UIkit as CSS framework. See https://getuikit.com/ docs (especially https://getuikit.com/docs/less) to get familiar with UIkit. It then adds several customizations to that CSS via less files that are located in the folder uikit-pw (see files on github).

The base style that is used for all styles (reno or rock or any other) is pw.less and you can even use the base style without any customizations if you want!

Creating your own styles

Creating your own styles is as simple as writing CSS/LESS. You just need to tell ProcessWire to use a different style than the default one:

1. Set config

The style property can not only take one of the two core style names (reno or rock) but also a path to a less file. This means we can build a custom style easily and simply point the config to that style:

$config->AdminThemeUikit = [
  // point to the new style
  'style' => '/path/to/your/style.less',

  // recompile on every page load during development
  'recompile' => true,

  // dont minify the resulting css to make it easier to debug
  'compress' => false,
];

Usually you'd put that directly into site/config.php. But to save you from copy&pasting and make it easier for me to load my style into my projects via GIT submodules I created a little autoload module that does the same in the init() method. See AdminStyleRock.module.php how that is done.

2. Create a LESS file for your new style

Now create the style file that you set in the config. Start with an empty file with a single comment like this:

/* ##### Admin Style Rock ##### */

Now reload your backend and you should see the base style of AdminThemeUikit without the changes that are applied by either reno or rock theme. You'll notice that it looks very similar to the default uikit theme:

That's it - you have built your first PW admin style!

If you look at the compiled CSS file (site/assets/admin.css by default) you'll see that the admin theme has over 16k lines of css and after that it adds the CSS of your style and after that it adds the CSS of admin.less.

Now you can start adding customizations/optimizations to your style.

Example customizations

Tweak PW notices

PW base style notifications look like this:

As you can see there are some margins that we don't want. We add the following line to our style:

.pw-notices {
  margin-top: 1px;
  > li {
    margin: 1px;
  }
}

Tweak page edit tabs

PW base style page editor tabs look like this:

Add this line to your style to remove the paddings:

.uk-tab>* { padding-left: 0; }

Changing UIkit variables

You can change any of uikit's less variables in your style. UIkit themes are built in components. See https://github.com/uikit/uikit/blob/develop/src/less/components/base.less as an example. Also check if your IDE has plugins to scan your project for LESS variables. I'm using VSCode + https://marketplace.visualstudio.com/items?itemName=mrmlnc.vscode-less

Changing fonts

Thanks to UIkit it is easy to change the base font. For this example we'll use https://fonts.google.com/specimen/Sigmar+One. All we need to do is to add the font to the styles array of PW:

$config->styles->add('https://fonts.googleapis.com/css2?family=Sigmar+One&display=swap');

IMPORTANT: For production you might want to download the font instead of adding it via google fonts to comply with GDPR!

Next, we set the correct UIkit variable - so add this to your style:

@global-font-family: 'Sigmar One', cursive;

Once reloaded you'll get a totally different look of your PW backend:

Changing colors

Changing colors is a little more complicated. I'll demonstrate why. First, we change the uikit primary background variable:

@global-primary-background: #610088;

Did you notice something in the screenshot? Links and hover colors are still the default blue. Same goes for the page tree:

So if we wanted to get a consistent color change we'd need to set more variables - actually a lot more and some of them are quite hidden, for example buttons of VEX dialogs that you'd likely miss to change if you needed to make all these changes every time you want to change the main color of your style. That's where the "rock" style comes into play!

The "rock" style

The goal of the rock style is to make it as easy as possible to adapt your backend to the CI of your client. That's why it uses only ONE single main color (@rock-primary) and keeps all other design elements in a neutral grey.

Now try changing the main color of the rock style by setting your config to use the rock style and then adding these two lines to admin.less:

@rock-primary: #610088;
@global-font-family: 'Sigmar One', cursive;

This will even change selection background:

Note that the global font family is not a @rock- variable because it would only change one single uikit less variable anyhow while @rock-primary changes many. To avoid confusion I think it is the best to introduce new variables only if they didn't exist or if they changed multiple uikit variables at once.

Contribution

If you find any spots where the rock style sould change additional colors or tweak paddings or margins please let me know! You can simply create issues or pull requests in this repository.

Once the changes are tested and approved I can ask Ryan to pull the changes into the core.