
There is no doubt that the brand spanking new admin interface in WordPress 2.7 is a huge leap forward, and so long as you don’t switch to the ‘blue’ version (seriously, worst, blue, ever) its actually pretty nice to look at and use. The navigation is now down the left-hand side, just as I preferred (which is why thats where it was in Fluency 1.x), and because of this, styling and customising the menu in-particular has been a lot simpler that it was in previous versions of WP.
So whats new.
Well, technically, everything is. Fluency 2 was a ground up rewrite due to the fact that just about every part of both the design and underlying structure of the default admin has changed. This was definitely a good thing, as it allowed me to make sure I’m only including what really needs to be included. However I did make this a little hard for myself when I started work using the early trunk builds, which meant that every time I updated my build I had to update Fluency…again. I actually ended up building the Fluency 2 CSS from scratch twice, and what it looks like now isn’t at all what it looked like when I first began playing around.
Ok, so whats “really” new.
Thanks to the addition of some extra hooks customising the style of the login screen is now possible, so that’s new.
I’ve customised the main navigation too, couldn’t help myself. You may have seen me mention that I’m not an enormous fan of the way the navigation functions. WordPress claim it take less clicks to get to different screens, but I don’t really agree. You still have to click a submenu to expand it, and then click the link, that’s two clicks which by my count is the same as before. Sure it require one less page load, but…
Also not a fan of the expanding/contracting width of the menu. I had played with, implemented and then removed pretty much the same thing in an early version of Fluency 2 before I figured it wasn’t worth the effort, and well before it appeared in the WP trunk. In the end I dropped it like a sack of potatoes because I didn’t see the point in adding it for the sake of adding it. After all it was only giving me about 80px of extra page width to play with. When it appear in the trunk I really didn’t like the way that menu behaved completely different whether expanded or contracted, and thought that it would surely be confusing for new users.
Solution. Custom flyout menus. Now virtually everything is just one click away (or a nifty key-combo…). Personally I love my new menus (as you would expect) they take up less room than the default one, and the behaviour has actually reduced the number of clicks. Plus I think they look awesome.
To go with the new menus I’ve added “hot keys” for quick access. Its the first time I’ve attempted such a thing and its turned out alright. As you would expect the hotkeys won’t function if you’re inside an input or textarea so your data entry should be unimpeded. I did however add these prior to the comment moderation hotkeys being added to the trunk so there may be some conflict there. If you find anything please let me know.
Unlike Fluency 1.x I haven’t had to modify the post screens too much beyond some cosmetic touchups. Besides, now that you can drag-and-drop all the panels on these screen so you can put whatever you want where ever you want it. Under the “screen options” menu at the top right of the screen you can also choose to hide some sections completely. This can be done on the dashboard as well as the post and edit screens, its one of the really handy features they’ve included in 2.7.
It should go without saying that the primary purpose of Fluency is to change the styles of your admin, all the other bit are just extra fun. While the overall theme of the design is similar to 1.x it much more refined, smoother and hopefully more consistent. The familiar grey colour-scheme is back, with colour added as needed. Little things like the inline post/comment edit/delete/approve/etc links are styled with appropriate colours, eg. delete = red, approve = green etc. For browsers that support them, ie. everything but IE, I’ve used rgba colours for menu backgrounds to give them a slightly transparent appearance.
Enough words, I should let you gaze across the screenshots below, and most importantly direct you to the download link (top right of this page for those that missed it).
Screenshots
I haven’t covered everything, but those are the main points. If you’ve got any questions just leave a comment.
Quick word about plugins.
Fluency has not been tested with ever plugin under the sun, I’ve test the ones I use, plus a couple of the more popular ones, but in general if a plugin has decent admin screens that follow the rest of the layout then it should be fine to use in conjunction with Fluency. If you come across a plugin that doesn’t, please let me know and I’ll do my best to add support for it in the future.





I tried it with WPMU and it works fine but there is a problem when you have an admin bar like for buddypress. The admin bar goes into the left panel menu of fluency. Would it be possible to fix it or is it a budypress issue ?
Its probably something I can fix in a future version, this version was not tested with WPMU or BuddyPress.
Hey guys, to fix Fluency for use with BuddyPress (using the word “fix” loosely) edit the following:
In Fluency’s wp-admin.css on line 36 you will find “#adminmenu {…}” in which there is a call to the Fluency2.gif background image. Delete the background information, including background color, and the admin bar will show through.
The final line 36 should read:
[code]#adminmenu {font-family:‘Helvetica’,‘Arial’;margin:0;width:110px;position:fixed;padding-top:40px;top:0;left:0;z-index:2000;}[/code]
Of course this removes the Fluency2 logo, so my suggestion is to add the logo back to the footer of the theme to give credit.
Like I said, this is a hack at best, but it seems to work.
~ GSN development
This theme looks damn cool. cheers mate.
Beautiful work! I thought the WP 2.7 trunk UI was nice until I saw how you improved it. Bravo!
AMAZING job
Will this work with WordPress MU?
Hi Dean,
Awesome plugin. Thank you.
I’m using Flutter cms plugin on a project and that’s when Fluency2 menu stopped working ie submenus didn’t flyout as usual. Is this something you can remedy or is it something Flutter needs to sort out? I’m using the latest firefox browser and wp 2.7.1
p.s. made a small contribution a few days ago – hope it was enough in AUD for at least a 12-pack of something good :)
I should be able to fix, or at least find a work around for, the flutter problem. Its possible that the flutter plugin is making some specific change to the menus (could be a simple css class or they might be changing the structure). When I have some free time (rare of late) I’ll download a copy of flutter and see if I can find the cause. And thanks for your donation, very much appreciated.
Take your time. I’ve decided to put off using Flutter until some bugs got under control. Thanks for making this plugin – saves a lot of clicks/time.
Great plugin, Dean! I’m happy to be able to use it again for 2.7.
I was immediately impressed with the slide-out menus and their transparency. I am running a local journal on a laptop so I spend little to no time on the actual “site,” making all my entries as an author in the admin panel.
A quick question– if I wanted to hack the plugin to change the background colors (no offense intended, I just can’t stand white), where would I look?
Also, someone was complaining about quick-keys and dual-digit submenus; could you possibly use a hexedecimal scheme so one could access up to 15 submenus using digits 1-F?
If you’re referring to the background colors of the page then you’ll probably need to either add some (and/or possibly change) some lines in the fluency css file. I’d recommend using the Firebug extension for Firefox to pin point which styles you might need to fiddle with.
So, what I’m seeing, then is default css values underlying WordPress itself? Basically the background white… I’d like to tone it down to a very pale pastel of some sort, perhaps lavender or mint.
I will look into that firebug extension, thanks!
Hi There — I have tried installing this and can’t get the flyout menus to show up at all. The left menu is there, the options just don’t fly out. I tried to figure this out from the comments below but haven’t been able to. Can you help?
Hi Justin, could you provide an info about what browser you are using and if you are getting any errors at all. Thanks.
Cool! I loveit!
i am looking for any plugin which take less time to edit posts in bulk
oh thank you for this stuff…
i am realy like it! great!
Hi — I love this plugin, thank you so much! I am using it for all my sites and adore it.
I’ve been asked by a client if they could have a custom login page — really I think they just want to stick their logo on it. Can you think of any way to accomplish this that doesn’t make it difficult to update your plugin in the future? Ideally I think I’d want an additional style sheet in the site’s theme folder, but I’m not sure how to accomplish this.
Thank you so much!
Hi Michelle, the quickest and easiest way to do this is probably to replace the wp_login.gif image thats in the images folder within the fluency plugin folder. This will allow you to swap out the WP logo for the clients logo and you won’t need to worry about touching and css or code.
Good! ))
This is a really great plugin; alas it seems not to quite work with my browser. I use Camino (kind of like firefox for Mac, gecko kernel but native rendering) and the spiffy black background is not there for the flyout menus. I wind up with a very light blue on white instead, which I can’t really read.
I poked around the CSS, and it appears that Camino can’t handle the *:first-child+html code. If I take the two following lines:
*:first-child+html #adminmenu li div.wp-submenu ul {background:#222;}
*:first-child+html #adminmenu li div.wp-submenu ul li a:hover {background:#111 !important;}
and paste in a copy of them with the first-child etc. chopped off, then things work perfectly.
I will do this for every release myself if I have to, because this plugin has saved me from endless irritation, but it would be lovely if there was some way to reconcile the code.
Its correct that those two lines should have no effect at all in Camino, as *:first-child+html is an IE7 hack, because IE7 doesn’t handle rgba background colours (which are used on the flyouts).
The light blue on white that you’re seeing is the same as what I was seeing in IE7 before adding those lines, so it looks like Camino doesn’t support rgba background colours either, I should be able to fix this for the next release.
I had the the same issue in Firefox 2. I tried your method and removed the *:first-child+html code from those two lines and now it looks great!
This is awesome! Any chance you could make it possible to offer a collapsible side-toolbar? When I’m using Fluid with the Fluency plugin, I’d love to relegate the toolbar to an icon/triangle in the top left corner of the screen to help me focus on writing.
Possible?
So your talking about collapsing it ‘completely’ as opposed to the default behaviour (without fluency installed) which just reduces each item to an icon? Can’t see any reason why it wouldn’t work, so I’ll add it to my list of things to look at when the time comes for an update. Thanks for the suggestion.
Hi, this is not working correctly with Opera. =(
yikes… i like the dashboard… but omg… if i log out… it really borks my home page… and never goes to that nice new login screen
Under what license is this sweet little plug-in?
don’t work here : i’ve no submenu… and font are very crappy.
Stef: why don’t you grow up and get a browser like Firefox where you can specify your own fonts on any website? It’s one preference setting away. (I have Helvetiva Neue and this plugin makes my WP look sexy as heck). Or just edit the CSS.
If you’re not seeing the submenu on the left, then you’re using another plugin that is conflicting with this one. Turn off all plugins that’re not serving an absolutely vital purpose (e.g., Akismet) and see if this works. It has to. Also make sure you don’t have any caching etc in your browser.
look strange : i’ve got submenu with local installation of my blog… but with the online one, no submenu.…( only if i use the wassup plugin + firefox )..
with IE, i’ve got the message : “jquery undefined”
:/
ok that’s work now.… Filezilla don’t upload some Jquery files.