Thread

Hey guys,

Today I’m opening up my override.css for the default control panel theme. I’ve tweaked a lot of things I personally didn’t like in the CP.

No doubt it’s not for everyone and there’s probably still a couple of issues. That’s why I’m asking for community feedback on a couple of things:

1. Browser support. I’m only supporting Firefox and Chrome ATM
2. Visual style: Is it something that your clients would enjoy using?

Leave your comments below.

Here’s the official release: http://ee-garage.com/override-css

Cheers Leevi

First impressions on this is looks great - thanks for the effort you’ve put in to it. I’ve added it to a site thats work in progress so if I come across any issues, I’ll post back on here as and when.

Visual style works for me - but its clients it needs to work for. I can’t see why clients would have any issues with it either to be honest. It’s a nice clean structure and doesn’t deviate too far from what they’re used to.

As far as charging, totally understand why you want to and I think I would be prepared to pay (with clients fees contributing of course). I wonder though if there’s enough difference from the default theme to make it worth while paying for though? Depends on the price 😊

Just found a slight issue too (I think) - screen shot attached.

Andrew

I wonder though if there’s enough difference from the default theme to make it worth while paying for though? Depends on the price 😊

My goal wasn’t to change the CP so much. It was to clean it up and make it more professional IMO. I was thinking around $20 per site or $60 for an unlimited license. Thoughts?

Just found a slight issue too (I think) - screen shot attached.

If you’re referring to 10px margin on the form that was intentional.

I think you’ve certainly achieved that goal then. I like it (and prefer it) so would be happy to install it for clients. Pricing I think is reasonable, but would perhaps be better if you had a couple of colour variations in the ‘package’.

I know as a designer I could go through and change colour values in the CSS, but how about including 2/3 different colour ways? I know a lot of people dislike the pink! I guess I could always find/replace the default colours to match in with a clients brand.

I would certainly rather pay for a well designed control panel than attempt to re-design it myself 😊

Absolutely love what you’ve done with all the styling for the CP.

I just went and added something on GitHub, hopefully I did it right?

Full credit to Iain though as it was his code that made this work.

Best wishes,

Mark

I think you’ve certainly achieved that goal then. I like it (and prefer it) so would be happy to install it for clients. Pricing I think is reasonable, but would perhaps be better if you had a couple of colour variations in the ‘package’.

I know as a designer I could go through and change colour values in the CSS, but how about including 2/3 different colour ways? I know a lot of people dislike the pink! I guess I could always find/replace the default colours to match in with a clients brand.

I would certainly rather pay for a well designed control panel than attempt to re-design it myself 😊

Colour schemes are out of the question. Wayyyy to much work 😊. The other reason is that if EL make a change it’s likely going to have less impact if I’m using a similar layout / colour scheme.

Ah just noticed something.

If I have your NSM Morphine Accessory installed and also this override.css file and the changes that Iain suggested then I get a weird issue with the menus happening (see attached image).

I’ve probably just done something a bit stupid somewhere so hopefully this can be fixed up so that the hover menus can start working again?

Best wishes,

Mark

Colour schemes are out of the question. Wayyyy to much work 😊. The other reason is that if EL make a change it’s likely going to have less impact if I’m using a similar layout / colour scheme.

Fair enough then.

If I have your NSM Morphine Accessory installed and also this override.css file and the changes that Iain suggested then I get a weird issue with the menus happening (see attached image).

I removed Morphine as I noticed some slight issues when I updated to the most recent version at the weekend. Nothing major, but the arrows in the dropdown was one of the things that happened.

Probably should have mentioned that this is going to be independent from Morphine. While testing please uninstall Morphine.

Probably should have mentioned that this is going to be independent from Morphine. While testing please uninstall Morphine.

Aha!! 😉

Excellent in that case as it (the hover menu) does seem to work fine without that installed. As you mentioned on Twitter perhaps the changes I was proposing (and that Iain created) could be an option for those that don’t like hover menus.

Myself personally I love them.

Best wishes,

Mark

I love Morphine and use it all sites by default - i don’t like all the overly rounded corners in EE default CP, so morphine cleans this up brilliantly.
In that sense, the overide.css file here is of little use as I’d take morphine over it anyday.

That said, the ability to do a find and replace on a .css file for colours to skin it closer to the clients site (or even brand it more towards moogaloo for eg) is very helpful, so if you do plan to roll this out to morphine too, i would happily pay a bit of money to allow that extra colour theming.

Further to that, I noticed you have specified the 7 or so colours that are used throughout the backend. Would this be a simple thing to build into a morphine accessory / extension settings page - you have colour names, and us developers / designers just plug in our #colour refs and it filters out to all instances, a bit like how twitter allows you to change the colours of your page - colour pickers would be too much - just a simple #colour field for each value would be enough.

all ideas…

First impression: Nice! Morphine made some changes that weren’t compatible with 2.1.3, this one is, so that is great. Still would love some non-pink template, orange or red or something like that would be nice.

The buttons on the top could have some more weight, had to look before i noticed it were buttons. Adding a :hover and a :active would be nice as well. In contrast, I find the pink submit buttons having a bit too much weight.

In general its a good improvement, making the CP a bit less rough.

I love Morphine and use it all sites by default - i don’t like all the overly rounded corners in EE default CP, so morphine cleans this up brilliantly.
In that sense, the overide.css file here is of little use as I’d take morphine over it anyday.

Morphine will no be developed in favour of this override.css. Consider the override.css a Morphine v2.

That said, the ability to do a find and replace on a .css file for colours to skin it closer to the clients site (or even brand it more towards moogaloo for eg) is very helpful, so if you do plan to roll this out to morphine too, i would happily pay a bit of money to allow that extra colour theming.

Further to that, I noticed you have specified the 7 or so colours that are used throughout the backend. Would this be a simple thing to build into a morphine accessory / extension settings page - you have colour names, and us developers / designers just plug in our #colour refs and it filters out to all instances, a bit like how twitter allows you to change the colours of your page - colour pickers would be too much - just a simple #colour field for each value would be enough.

I don’t plan on adding any colour ways to this override.css. The added support development would be way too much. That said I’d be happy to create a fork and allow a private collaborator to keep the additional colours upto date.

all ideas…

If you are discontinuing Morphine are you going to fix the settings panels for your extensions to not look terrible without it.

I had to setup Better Meta for a site today and the extension settings panel is a mess without Morphine, but Morphine doesn’t work properly with 2.1.3.

Found an issue on the add/edit custom fields within a channel - there’s a massive top margin!

Same applies on the page after submitting a new entry.