Branding the PW admin panel

[mike77]

I'm starting new project for a first time with PW. I'd like to know if it would be apprioprate (in terms of PW's creator permission) to brand the admin panel with clients logo just to make the look of it more relevant to the clients CI. The PW logo would stay where it is now but I thought of adding one next to it or something.

Is it technically possible?

[arjen]

It is possible. The ProcessWire cms is basicly running on ProcessWire. There were some discussions about this topic a while ago.

[mike77]

The ProcessWire cms is basicly running on ProcessWire.

It doesn't mean you're allowed to do whatever you want with it. But thanks for the link. Cheers.

[diogo]

Is it technically possible?

Arjen answered directly to this question.

The link he pointed to can help giving some answers to your other concern.

[arjen]

You're right mike77. It doesn't mean you're allowed, but since it's technically possible it can be done.

[ryan]

I'm starting new project for a first time with PW. I'd like to know if it would be apprioprate (in terms of PW's creator permission) to brand the admin panel with clients logo just to make the look of it more relevant to the clients CI. The PW logo would stay where it is now but I thought of adding one next to it or something.

To do this, I'd suggest copying the contents of /wire/templates-admin/ to /site/templates-admin/ and then make the edits to your version in /site/templates-admin/. That way it won't get overwritten during upgrades. However, sometimes the admin theme does get updated, so you may want to note the edits that you make in case you need to make them again during a future upgrade.

[mike77]

Thanks Ryan - sounds easy. I thought that only the config.php in 'site' folder acts this way but it's good to know that more files can be edited and protected from override process during the upgrade.

[ryan]

Anything that is under /site/ is protected during upgrades. These are all your site-specific files and PW doesn't mess with them.