Fluency Admin 2.0

Fluency 2

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.

Please leave your name and email, so we can show off your gravatar


HELP! For support questions please visit help.deanjrobinson.com →

190 Comments on this

  1. We’re running the latest version at Chewru.Com — we love it. A couple bugs, maybe:: When I finish a post and publish it — the visual view (not the HTML view), goes entirely white. If you highlight the ‘empty’ box you see the text, but I can’t get it to come up otherwise (forced to edit in HTML going forward). This is a CHROME-only issue as far as I can see.

    In IE8, I can see the text that’s blank in chrome, but the mouse-over menus dont pop up. It looks like it tries too — it builds the frames for the text that should be in there — but they’re blank. The only keyboard shortcuts that show are NUTS — kind of funny.

    Please keep working on this admin backend — it’s great so far!

  2. You have to correct something in your description: if you choose the minimal look in the new WordPress administration, you don’t have to click to develop the tree.

  3. This looks great! I was impressed with the WP2.7 admin page already, but somehow you’ve found ways to improve it even more. Great work!

  4. Look good but left sidebar is gone in IE8 Beta2.

  5. Hey, your plugin is so nice!

  6. Oh, Man, this is beautiful! I was really bummed when I upgraded to WP 2.7 and had to deactivate Fluency Admin, but you have made something really cool, here.

  7. Unfortunately, the left column is not activated in Firefox — or at least not in the theme I’m using.

  8. I see some problems with Safari rendering buttons (edit, delete…) when viewing list of posts. Because of that height of specific post is to big.

  9. Just installed the Fluency Admin 2.0 and this rocks! Very well done and user friendly. Sharing with other people as a 5 start must install.
    Thanks!

  10. A very nice Admin Theme. I used it in my technic blook and i love it to work with.

  11. Very cool. I didn’t think you’d continue fluency after 2.7!

  12. This is an amazing admin theme! Thank you so much for creating and working on this. The hover over effect is excellent and the keyboard shortcuts are a great time saver. Just plain awesome…

  13. Wow, this is simply great.

    I’m a web designer, and wordpress is obviously my cms of choice. I’ve been looking to use something like this for a long time.

    Anyway i could package this with client work? Just to spice up their final product? I know a lot of clients that would prefer logging into something like this, rather then logging into that default wordpress blue!

    Please, let me know at paul.unr (at) gmail.com

  14. What I was wondering is why every menu item got it’s shortcut except for the comments. The reason for this is probably that the comments don’t have a submenu, right?

    Yes, thats correct. Comments would have a hotkey if there was a submenu, as the top level hotkeys are only used to activate the submenu. I’ll look at changing this in a future update.

    Personally I can’t figure out what the Akismet menu doesn’t live under Comments, that seems weird to me.

  15. Nice, I’m quite overwhelmed how you managed it to top the also very nice default design. And with the keyboard shortcuts I can finally sale my mouse :)
    What I was wondering is why every menu item got it’s shortcut except for the comments. The reason for this is probably that the comments don’t have a submenu, right? But I think it would be nice to have a shortcut for this also.
    Plugins getting a main menu item obviously don’t get a shortcut. Perhaps it would be nice if one could configure such shortcuts by one selfs.

  16. FYI: Before plugin activation, make sure that the original menu is expanded. Otherwise it will be hidden. There are also transparency issues in Opera, I guess because of Firefox specific CSS-rules.

    Most of the transparency is done using rgba colours, which both Firefox and Safari handle, for IE it should use solid colours. Based on your comment it sounds like Opera may not support rgba.

    In regards to the expanded menu, I actually intended to add some code to make sure that it was set to expanded but I ran out of time to add it in.

  17. FYI: Before plugin activation, make sure that the original menu is expanded. Otherwise it will be hidden. There are also transparency issues in Opera, I guess because of Firefox specific CSS-rules.

    Great work otherwise, apart from the gorgeous design, I especially like the keyboard shortcuts for menu navigation

  18. I’m not seeing any text other than the post title, but I’m hoping 2.0 means a WP2.7 compatible version? In which case I’ll grab it as soon as I’ve upgraded.

    Indeed it does, you just happened to drop by as I was uploading the new version.

  19. I’m not seeing any text other than the post title, but I’m hoping 2.0 means a WP2.7 compatible version? In which case I’ll grab it as soon as I’ve upgraded.

1 2 3 ... 6
twitter was not updated. | lastfm was not updated. |