CHAPTER 9 • Using WordPress As a CMS 225
◾ Product support: Another common criticism against open source CMS alternatives such
as WordPress is that commercial products offer support as part of the package, making it
worthwhile to pay for a CMS. The counterargument to this is that the money allocated to
licensing could be spent on a consultant and/or developer when needed, and not just be
the cause of a big hole in the coffers. You can take those licensing fees and build your
adaptations, should you not find the solution available already. And after that, it is all free.WordPress is a great CMS option, especially if you’re building an editorial site. Whether
or not you think it is right for your project, you should always sit back and figure out what
you actually need first. Then find the ideal CMS and consider how you would use it for
your particular project.
WORDPRESS CMS CHECKLIST
So you’re considering using WordPress as a CMS for a project? That’s when the following
checklist comes in handy. You need to think about these things first to avoid running into
unwanted surprises along the way.
The first questions
◾ Do you really need a CMS for this project? Sometimes hacking HTML is the way to go,
after all.
◾ Is WordPress the correct CMS for your project? It may be great, but sometimes other
things would work better to meet your needs.The WordPress admin interface
◾ What additional functionality do you need for the admin interface?
◾ Should you use plugins (or custom code) to cut down on functionality? The admin
interface can be overwhelming to less experienced users.
◾ If you’re going to employ user archives, consider what usernames to give everyone
involved because this will appear in the URLs in particular.
◾ Do you need features for menu editing, custom backgrounds, and custom headers?
◾ Does it matter that the admin interface is branded WordPress? If yes, you need to give it
some new style, and don’t forget the login form.Categories and tagging
◾ What is your strategy with categories and tags? Do you need to add further taxonomies,
such as separate tag groups or hierarchical categories, to make the site work? Do these
taxonomies need to be portable when the site changes themes in the future?
◾ Which categories should you include, and do you need custom category coding and/or
templates?
◾ How should tags be used, and how will you educate the users in the praxis you’ve chosen?