WordPress FTW! ...most of the time.
Updated July 07, 2015

WordPress FTW! ...most of the time.

Ansel Taft | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Software Version


Modules Used

  • A cache of ~30 plugins we routinely use

Overall Satisfaction with WordPress

We use WordPress as our primary platform for new client sites. Our bundle consists of probably the most respected of the premium WordPress theme frameworks, custom graphics from our design department, a set menu of plugins, custom programming to make certain features sing, and responsive styles baked in by default. Our development stack allows us to bring client sites to life in a week or two at a competitive price point, while delivering a decent feature set with a totally custom design.
  • WordPress can handle a broad array of content-centric sites from static sites, to a blog, to a mixed media site, to a content heavy site like TechCrunch.
  • Most mainstream site scenarios can be built using WordPress, up to the point where a high I/O or real-time webapp needed instead.
  • High I/O or real-time webapps.
  • High concurrent user sites. The server environment would need to be tuned to handle this, but the same can be said for most development platforms out there.
  • Wordpress as a framework or other MVC-style sites, the tools are still in their infancy.
  • WordPress' core is slowly being refactored from procedural to OOO-based code.
  • Our customers' ROI has been excellent. The local businesses we serve are able to be found by the business name and generally rank well for a variety of local search terms. We are also able to build out landing pages quickly and easily and then marry them to a variety of direct mail, social media, and PPC campaigns.
My CMS journey started with Drupal, then Joomla, then moved on to WordPress. With Drupal I felt like it was built by software engineers for other software engineers. Its dashboard was cumbersome and felt needlessly complex. Joomla's dashboard on the other hand, felt like a scattered mess of organized chaos. Our company took on a few Joomla clients the past year and even with familiarity, we spent an inordinate amount of time hunting and pecking through various pockets of content to find where to make changes. Not to start a flame war, but if anyone reading this thinks that Joomla's dashboard is in any way superior to WordPress, I can assure you that it's due to a lack of familiarity, a state of denial, or an unwillingness to consider what the other camp has to offer.

Dashboards aside, all three are modern CMSes with comparable media abilities, themes, third-party integrations, plugins, custom post types, etc.
What is the purpose of the site?
What types of content will be served?
For how many users?
Will they need different access levels?
How many monthly visitors are expected?
How many concurrent users?
Will you need e-commerce baked in?
For how many SKUs?
Do you consider mobile users important to your online strategy?
Will the site need to be responsive?
How important is SEO to you?
Do you plan to advertise the site with PPC or on social media?
How will the site need to fit into your social media strategy?

WordPress Feature Ratings

WYSIWYG editor
Code quality / cleanliness
Admin section
Page templates
Library of website themes
Mobile optimization / responsive design
Publishing workflow
Form generator
Content taxonomy
SEO support
Bulk management
Not Rated
Availability / breadth of extensions
Community / comment management
Internationalization / multi-language
Role-based user permissions

Using WordPress

We will continue to use WordPress until something better comes along. I've heard good things about a CMS called ProcessWire that's build on a modern OOO and MVC framework, but the speed of development needs to match what we can do today with WordPress.