Nowadays most business websites have a Content Management System driving them so their owners can make edits without having to go back to the original web developer. They have become sort of the norm and most business owners request such functionality when purchasing a new site.
If you hire the right web developer, the process of building such a site will be smooth with your having to make some key decisions along the way. However, regardless of how great your web developer is, he will eventually require content from you.
In the past, with static websites, content could be provided in simple Word documents, or even in a mismatch of electronic formats. The developer copied it as a large chunk and pasted it on the corresponding web page.
With CMS-driven websites, preparing content is different and it has a process of its own. Before getting to this process, we need to go over how CMS-driven websites actually work. Whether you are using Drupal or WordPress, there is a crucial hierarchy that must be understood in order to think about and prepare the content for all pages of your site.
1. Themes
The theme of your website is the actual design. Even though different pages may look different in terms of content and layout, a consistent theme ties them all in with similar colors, navigation in the same place, similar design treatments, etc.
See below for MB/I’s theme. All 5 pages selected have different images, content, and even layout but you can tell they all belong to the same website. The theme is what creates this visual consistency.

2. Templates
Now we start breaking the theme apart. A theme consists of several templates. A template is a specific and unique layout regardless of the actual content it will display. Think of a template as a “container.” If you fill a glass with water or with orange juice, the content does not change its nature. A glass is still a glass. The same goes for templates.
Look at our own portfolio template below. This one template is used to display whichever sample work we want, but it always has design and element items in the same place.

A key decision you will have to make is how many templates you will need for your site. Since each template has to be designed and then programmed, the final cost of your site will increase for each additional template. Typically we build websites with anywhere from 2 to 7 templates.
3. Content Types
Here’s where a CMS-driven site really differs from a static site. Developers think of content in terms of content types. Let’s stay with the portfolio example above. Since the portfolio is not just a simple page of text, we created a unique content type for it. This content type is made of specific fields, each field corresponding to the information we want to display on the website.
Following our example, for our portfolio content type, we need to capture information for all of these fields:
1. Name of the client
2. Website URL
3. Industry it belongs to
4. Services we provided
5. Testimonial (if provided by client)
6. Credits (if we partnered with another vendor)
7. One or multiple screenshots of the work we did
4. Views
Now that we start seeing how content types work, we can take advantage of what a CMS-driven site is best for leveraging content. A view is simply a different way to display the same information.
You can see below that 3 different templates on our site display a thumbnail representing a portfolio item with its corresponding client name.

This information is coming from the portfolio content-type. It is simply being displayed in a different view. Same content; different display. The crucial thing to grasp is that you need to think of all the different views you want for each content type so the developer can create a complete list of fields.
In our example, we need to add a thumbnail to a list of fields. So, our content type now consists of:
1. Name of the client
2. Website URL
3. Industry it belongs to
4. Services we provided
5. Testimonial (if provided by client)
6. Credits (if we partnered with another vendor)
7. One or multiple screenshots of the work we did
8. Thumbnail image
You want to think about this at the beginning. It’s true you can add fields later, but that’s inefficient for both you and the developer. The developer has to backtrack and program new fields and views, and you may have to go back to several portfolio items and 1 by 1 add the thumbnail image.
Preparing Content
Now that we understand this hierarchy we can see that providing long Word documents doesn’t work very well. First, you might miss fields you need by following this approach. Second, it’s more time consuming for the developer to copy and past content this way. Third, the developer may make mistakes entering content since the fields are not specified and your content may not be consistent within a Word document.
The best way to provide content for content types is via Excel files. See below for the Excel file that would correspond to our portfolio example.

At MB/I we provide these Excel template files to our clients. Even though it takes us a little more time up front, it helps us communicate better with our clients and it makes content entry much easier in the long run. Most CMS have the ability to quickly import data directly from an Excel file, so no one has to take too much time copying and pasting content one entry at a time.
Finally, when the CMS is delivered to you, you will see how it also fits exactly to the fields you’re already used to. See below for a glimpse at a portion the corresponding CMS back end page for our portfolio entries.

If you’re purchasing a CMS-driven site, make sure you walk through these concepts with your developer. You want to understand how your site works and how you will need to prepare your content. It’s not just about writing the content any more, it’s about the organization and display of it.
Recent Comments