Since publishing more content for WPTavern, I’ve become quite fond of the ability to schedule posts into the future. However, one gripe I’ve had is not being able to easily identify the time a post has been scheduled to be published. I was hoping that at some point in the future, on the All Posts administration panel that I would be able to see the time the post was going to go live under the term Scheduled, instead of having to go into the edit panel for the post to see the exact time. My mouse cursor must have been at the right place at the right time because I discovered tonight that if I hover my mouse cursor over the date the post has been scheduled, a tool-tip will appear that gives me the exact time.
It’s little things like this that I really appreciate.
Meg Heckman of Poynter.org shares her experience from a newsroom perspective with The Monitor using Drupal while sharing the experience of William Davis of the Daily News and their move to WordPress.
So which system is better?
Neither.
The question of WordPress versus Drupal isn’t Coke/Pepsi, boxers/briefs, Red Sox/Yankees. It’s about understanding the needs of your organization.
The five questions brought up within the post are definitely ones you should have answers to before making any decision to go with a particular platform. As a bonus, check out the comment left by pmaiorana who claims to work for Automattic with regards to the important factor of software updates.
With such head-starts, the five figure medium-sized website cost quickly becomes four. The four figure small business website cost becomes three. The home-grown sideline business goes from three figures to two (many premium WordPress themes designs are available for only $50). You can even get a WordPress website on their sister site for free. Buy a domain name for it and you’re in business for just $10.
To the short-sighted web developer or designer it’s the end of days. To the business owner it should be the start of getting the website they always thought they were going to get, but never quite did, for a price they can justify, and that everyone can use. via – WordPress The Quiet Revolution
LinuxInsider.com has a great case study published from the CTO of eMusic.com, Richard Caccappolo on how the website transitioned from using a clunky CMS to WordPress. While reading the case study, the first thing that struck me was the following: “we found that WordPress was an ideal solution to suit all of our CMS needs.” Anyone who STILL thinks that WordPress is just for blogs really ought to change their mindset. While reviewing the different CMS solutions available, Drupal became a strong candidate but thanks to the persuasion of Scott Taylor who is the lead PHP developer for eMusic, they opted to go with WordPress instead. The case study goes on to describe tips on ensuring a smooth transition, why plugins are both a good and bad thing, and how eMusic decided to use bbPress along with BuddyPress to provide a more flexible platform for their community. After reading the case study, stop back and watch Scott give a presentation on the transition process from WordCamp San Francisco 2011. Watch in full screen mode to read the slides.
If you could ask Scott a question or two regarding the huge transition, what would it be?
Aaron Brazell who heads up Technosailor.com has published a primer on how WordPress Subversion is organized. The primer explains trunk, branches, and tags with regards to what they mean for developing WordPress. Also worthy of reading is Andrew Nacins comment located under the article as he offers more clarification on the use of branches. ∞
Interesting discussion taking place over at WPBeginner on whether or not the Blogroll Links functionality should be removed in favor of Menus. Outside of their discussion, I’m in favor of ditching links. In fact, I think the links functionality should be turned into a core widget because that is where most of them end up anyways, in a sidebar as a widget. So while the functionality would still exist, it’s one less item in the menu. Any thoughts? ∞
I love the concept behind this list. WordCamp Orange County organizer and WordPress developer Brandon Dover has compiled a list featuring some of the craziest excuses he’s heard for not upgrading WordPress. However, the list also includes reasons that have been submitted by readers. As of this writing, there are 23 reasons listed. My favorites so far are 5, 6, 15, and 20. Keep in mind when reading the list that the page is a joke and while some of the reasons are certainly legitimate, others such as My mom told me not to are clearly not. The list certainly got me to laugh out loud a few times.
I hacked core and didn’t submit a patch. *GASP*
I like feeling vulnerable.
I’ve been living under a rock.
I don’t want to be a cool kid.
Maybe at some point, Brandon can find a catchy domain related to this joke and make a simple page that randomly shows a reason not to upgrade WordPress complete with a form that takes user submissions.
WordPress has a smaller community than either Drupal or Joomla, so you may not find be able to find the help you need. – Not sure who could agree with that statement, especially after reading this report which is about a year old but most likely, still relevant. Regardless of the report, I’d love to hear anyone back up the claim that WordPress has the smallest community amongst the two. ∞
I have no idea what it feels like to get a patch committed into WordPress where millions will take advantage of it but it has to feel pretty darn good. At least that’s what it seems like according to Coen Jacobs who recently had his first patch added to the core of WordPress. Congrats Coen. Hope this is one of many more to come. ∞
Theme.FM has a great writeup explaining one of the new features that is slated to arrive with WordPress 3.3 called Pointers. These pointers appear to show the end user some information related to a new feature. However, it looks as though in future versions of WordPress, there will be an API built around pointers which should allow plugin and theme authors to tap into it’s usefulness. If you don’t like the pointers feature, WPEngineer has an explanation as to how to disable it. Keep in mind though, that the information is based on the nightly build of WordPress so the implementation could be different later on. ∞
