Joomla Project Costing - Hosting Setup and Joomla Install

By Justin Kerr
July 01, 2010

Table of Contents

Hosting Setup

Qualification of a Web host and/or configuration of the Web hosting environment is a common task for Joomla projects, especially when working with SMB clients who may not have a Web hosting environment appropriate for Joomla. Depending on the project, the hosting vendor and the client, prepping the environment for Joomla can take from a few minutes to hours of time. No matter what, it is best practice to make sure all hosting environment variables are optimized early on in the project: If they aren't, it's almost inevitable that the issue will have to be addressed at some point during the life of the Web site, and fixing it later will almost always be more costly than working with a proper configuration from the start.

Do not forget to accommodate tasks that might not be part of the "Web hosting" setup per se, but in the client's mind, they'll expect you to assist anyway. For example, many SMB clients will need help with domain registration or DNS configuration; a larger client may have project requirements that necessitate a development server. Anything to do with e-mail should be broken out as a sub-project and priced to accommodate the hassles of spam and dealing with users and their accounts.

Joomla Installation

Let's face it: Installing the basic Joomla CMS is a breeze, especially when working in a properly configured Web hosting environment and pulling from previous Joomla installation experience. This process should take well under an hour: even just 10-15 minutes or less for experienced admins.

However, most Joomla service providers will augment every core installation with a set of extensions that provide commonly needed functionality. (For example, almost everyone will replace Joomla's default WYSIWYG editor with a more feature-rich editor such as JCE.) Each provider should establish their own set of "must-have" extensions for their clients' sites, and calculate the cost of installation and configuration. One way to mitigate some of this extra cost is to use a Joomla extension like Akeeba Backup or XCloner to clone and migrate a "default" starting setup from a development area to a new Joomla installation.