So in part 1 of this series, we discussed the design phase of a website. An exploratory interview with the client has already been had and a graphical mock-up of the site has been refined and approved for development. This brings us to actually building the site.

As mentioned earlier, the push-button web creation function, provided by graphics applications like Photoshop, will not produce an optimal page structure or take into consideration forward-looking steps that will allow for a versatile and scalable website. During the design process, the designer/developer will have already mapped out the solutions for various site features and layout configurations. Given the different requirements surrounding these features, the site structure will be created to accommodate them.

Take a simple two column site layout for example. As the height of these two columns changes with varying amounts of content over time, how do the the columns behave? Does the overall site design depend on these two column expanding and contracting together or is it better suited to have them expand independently? Furthermore, do the pros of a table structure in this scenario outweigh the cons and what impact will this decision have on cross browser compatibility?

At this point, the considerations of structure have been made, the developer knows which language will be employed (according to their own expertise or perhaps simply based on the hosting server being used), and the site’s ongoing maintenance and accessibility has been factored in.

By this I mean, who is going to update the site and how? Even if the site is being built by an in-house developer who will maintain their own code, it’s simply not time and cost effective to maintain and grow a site from code view. Which bring us to building the site on a CMS (content management system). A CMS allows the site to grow gracefully, protecting sensitive code and maintaining the site design, while giving non-developers edit access to the site. There is a vast field of CMS’ out there to choose from and the one that’s right one for you will depend on your need. The demands of an online news agency, for example, will differ greatly from that of a local book club. Either way—big or small, high volume or low—a content management system is an absolute must.

Consider that we, professional web developers, use a CMS on everything internal that we build. Believe it not, I still see ads being placed by cost-conscious small business owners seeking low cost developers available to make frequent and ongoing edits to their site. That’s crazy! Done right, on the right platform and by the right developer, the upfront cost of building a site on a CMS is negligible compared to keeping a professional developer on payroll. In fact, when done right, the cost of building on a CMS can often reduce the cost of a project by allowing for quick replication of pages and page features as well as allowing the developer to set aside a majority of the content entry task for the client.

To be continued… We’ll continue our discussion of the development process in part 3 of this series. To be covered are site features, functions and integrated applications.