Drag to your bookmarks bar, click, get a bunch of buttons for easy access to specific areas of your WordPress admin. No security concerns, other than taking people to your log in page, so assuming you have a good strong password you are fine. Also I suppose this assumes you have WP installed at the root...
WordPress has a bunch of AJAX abilities built in that you can access, without having to use any outside resources. Gary Cao shows how, pointing out good and bad practices.
Update: (404 link removed 2013/11/20)
Marcus Neto attempts to compares the two CMSs while explaining why he likes ExpressionEngine. Are they really apples or oranges? I suppose you could say that. Apples and oranges are both popular spherical fruit. They have more in common than theyhave different. Same with the two CMSs.
While I'm 98% a WordPress guy, there are a few circumstances I might take the EE route, like when:
- I knew I was going to need a whole bunch of different custom data types and groups and didn't feel like dealing with the whole Pods or Flutter setup.
- I also knew no newbie client was going to need to get in there.
This is me trying to understand it:
Instead of services that read your feeds (e.g. Google Reader) having to ASK for your feed periodically, now they can instead just wait until YOUR SITE notifies THEM. Basically a "push" service.
It seems to me this is half the equation. The other half is building services that accept these push notifications. I'm not sure who is already doing that, but I wouldn't be surprised if Google is on it, since it seems like a more efficient way of doing things on both sides (less server resources on both sides).
Two concerns I can think of:
- Is this just as reliable as the "old" way? People not getting feed updates because of a hiccup in the chain sucks for everyone.
- This makes "accidentally" hitting that publish button potentially even more embarrassing than it already can be. Like when you accidentally publish a post instead of a page.
Also check the overview slideshow here.
This is basically a smarter way to handle the situation I just posted about. Using a function to manipulate the favorites dropdown instead of a core hack.
Update: (404 link removed 2014/04/29)
If you want to use BuddyPress (a massive plugin that basically adds a social networking layer to WordPress sites, think, forums, profiles, user blogs, etc) but you've been hesitant to try it, now is a better time than ever.
BuddyPress 1.2 now works with stand-alone WordPress installs (before you had to use MU) and you can even keep your existing theme.
kristarella has a nice article on writing your own custom loops.
Here are two ways to include HTML5 elements in your WordPress post content without WordPress’ wpautop function wrapping them in p tags or littering your code with line breaks.... Both ways rely on hand-coding the HTML5 markup in the WordPress editor’s HTML view.
Great crash course article on theme building from Chris Spooner.
One of the things I hear people desiring from WordPress is some kind of system for customized installations. So when you go to install a fresh copy, all the settings are how you like them (among other things).
Thomas Scholz has a sweet solution here to get us nearly there. It's a plugin that you install, activate, and delete. All it does is reset your settings how you like them (you customize it), and delete the "dummy" post and comment.
Our WordPress themes offer you infinite customisation: just drag and drop. Beautiful sites are now for everyone. Customisable sites are now for everyone.
Then almost immediately after the WPShift tweet, Ben Gillbanks announced his newly acquired and freshly redesigned WPVote (404 link removed 2014/05/30) site, where the WordPress community can submit and vote for their favorite WordPress posts. Think of it as way better than Digg for WordPress.
Both Alex and Ben did a tremendous job with their new sites. Congrats to both!