Please make the EE3-CP themeable again, or at the very least provide a built-in way to provide a custom CSS file (Bonus points for providing your original .less file). Blue is a nice color and all, but it’s not always appropriate …
Apart from hacking the minified CSS (ugh!) there’s an extension that does some of it, but a native solution sure would be appreciated.
Hi Ingmar,
We are working on a CSS color changing UI for the CP, that will allow you to change colors in the CP, but not structure. We believe this feature will give folks the majority of control they want over the CP aesthetics, without having to edit CSS or LESS files.
Thanks for the feedback, we appreciate it.
@Jeremy S. We have to weigh each and every feature requests against itself and the rest of the app. Features that help the most customers garner the highest priority. We think every request is valid, and that a lot are things that would be great for the app to include.
Our team is small, and we have to be able to say no, and push things to future versions to make room for the higher priority things in each release.
That said, we understand that what we prioritize isn’t necessarily going to be the same decision you would make, and we respect your right to be disappointed about that and will hear and listen to your complaints. We’re just asking or a little understanding and patience, especially on the things we are building, but maybe not in the timeframe you’d like.
So that I can better understand where you’re coming from, can you expand a little on why you feel that we’re slowing down?
I’m not sure I’m seeing enough features being added that benefit the end-user, our clients, who we ultimately recommend and sell the product too. EL’s done a great job and come a long way with 3, but there are still standard EE2 (and even EE1) features missing that client’s need to even sell the EE3 upgrade and many of us thought we’d have by now, like better CP search filtering and bulk status updates. These are 2 key features for any organization with more than a couple employees producing content. It existed in 2 and shouldn’t need a 3rd party or custom dev to try to have it in 3.
I would hope bulk uploads are a priority in the future, it’s a pretty common CMS ability and shouldn’t need a 3rd party. How about little things like being able to set the width of grid fields in the CP like we used to. It’s not an ability incompatible with responsive design with min-widths and/or ignoring the set values at a certain breakpoint.
At the end of the day, the excitment of ee3 was knowing you were working on a responsive CP, reworking or a lot of code for performance and streamlining things for extending EE. Excellent. But how about the tail-end of ee 3 or big goals for 4 (without over-committing yourselves of course). I’m sure many of us want to keep having an idea where things are going.
But if I am looking at this the wrong way, I am open to the community’s thoughts.
P.S. The criticism comes from a place of love for the product 😊
@Jeremy S.
I can tell you that we’re all working hard to continue to grow ExpressionEngine, and improve it’s offering. And we always appreciate the feedback and insight into the customer’s thoughts.
We want everyone to be happy, but we can’t focus on every issue simultaneously, so we also count on patience and understanding while we solve the problems to the best of our abilities.
A more robust edit entries UI is coming, with bulk editing, and better search and filtering.
Bulk uploads and drag and drop and other File Manager improvements are on our list as well.
Better publish form layouts will be making a return too.
Things we are working on currently all move us towards those features, done right. We are working, and releasing faster than we ever have. Getting to 3 took a long time. We are working on 3.5, and then after that focus is on 4.0 (and that doesn’t necessarily mean there will be an upgrade cost). Just as an example that we are pushing faster and farther than ever before.
We have a lot of things we want to build, but not unlimited time, so I’m going to get back to it.
Thanks again for the feedback, we truly appreciate and listen to it all.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.