Thord Daniel Hedengren over at Devlounge has published an extensive checklist based on his experience of things to consider when using WordPress as a CMS, especially when it will be used for a client. His post covers a number of different situations you should think about ahead of time before you step into your favorite code editor. According to Thord, there are three things you need to consider before committing to WordPress:
1. Is the functionality needed covered by the WordPress core functions, and/or with the addition of (not too many) plugins? This is usually managing information pages (using Pages), and publishing news/press releases (using Posts). If I need to add a lot of custom stuff, including the custom fields, then perhaps it gets too complicated for the client.
2. Is there a good translation of WordPress available, so that your client can get the backend in their own language? Why should my Swedish customers not have their CMS in Swedish? There is no reason, of course, and it is easy enough to install a language pack.
3. Will my client be able to upgrade WordPress themselves, or do I need to make plans for this as well? This is true for most platforms out there, but nevertheless you’ll need to have an upgrade strategy.
I’ve never dived into the realm of setting up WordPress for a client so this is all new to me. However, I know a lot of you install and configure WordPress for your own clients. With that in mind, I’d be interested in knowing your own checklist of things to consider before committing them to WordPress.