While I built the framework and the base design, the hard work was done by Dan and Elise. After only a two hour training session with myself (and a few follow up emails) they managed to master the job.

The site is built on WordPress with some carefully selected plugins to enhance functionality and some tweaking of the theme to render a viable content management system (CMS).

Down the line I will be helping Dan and Elise roll out the ability for supporters of the foundation to make donations and to purchase goods from their shop online.

Pop by and visit. You never know – you may just see a dog or cat in need of rehoming and fall in love.

These are the type of questions I am asked over and over again. I can never answer.

Would you ask a builder how much they’d charge to build you a house? No. You would show them the plans. You would discuss the materials and what work, such as the kitchen, you’d like them do and not do. Possibly you would state your budget. And so on.

Once the builder understands your requirements they can draw up a quotation. The same applies to web development. Until I know what you want I cannot give you a price.

Ideally the first approach should be statement-then-question: Here is what I need. What would you charge me?

However, more often than not I find people do not know themselves what they want or need. That is not a problem. We can sit down and analyse your requirements, thereby defining the “here is what I need” statement.

Then the “how much does a website cost?” can be easily answered.

As an aside, on seeing a CMS in action, a client in the haulage industry once misconstrued their typing and clicking as web development and proposed he come into business with me. I can do this. It’s easy. We could make sites for other truckers.

Luckily this was pre-Obama and I didn’t reflexively say yes we can thereby saving him a lot of pain and anguish, not to mention a doomed business.

CMS is wonderful and it is empowering.

However, if one is unable to dedicate the time, no matter how little, to managing it, it can be overpowering. For some the novelty wears off and they lose interest.

I have received calls on occasion from clients asking me to add some piece of news to their website. Why, when they can do it themselves? Because they don’t have time.

Of course I oblige. But I have to charge for my time. More importantly this defeats the purpose of a CMS.

These days I am more conscious of this and take greater care when considering recommending a client use a CMS.

I stress to the client that using a CMS requires a long term commitment.

Using the terms blog and theme has led many to believe it can be downloaded and used to dress up a blog straight from the tin. This is true – it can be if that’s all you want is the vanilla framework.

But the early adopters tend to be those who will find the bugs and try to fix them, or will want to customise by stripping out or adding in a line of code here and there.

Carrington is not like any other existing theme and attempts to tweak it as if it were will usually result in frustration or fail totally without an understanding of how it works. Alex King has been at pains to explain to those who complain it is not user-friendly that “Carrington is a theme framework; it is designed for developers”. [Source: Crowd Favourite Forums]. He must be blue in the face doing so – then he does live in Denver and it’s damn cold there.

That said, many must be happy with it. In little over a month since it was made available on WordPress.org there have been 14,000+ downloads. I am one of those happy people. In fact I’m more than happy. And I’m excited about what the next releases will bring.

Carrington takes the abstraction of WordPress tags to a new level.

Those who are familiar with WordPress conditional tags will be used to doing things such as adding code to the header.php file do make it act differently if what’s is being loaded is, for example, if it’s an archive page do something; do something else if it is a category page; and so on.

Depending on the complexity of what one is trying to be achieve (and the quality, good or bad, of the algorithm employed) this can result in a lot of code.

In Carrington this is done by creating separate archive.php, category.php and so on, files within the header directory. The process is as simple as copying the default-header.php and tweaking as needed.

Carrington automatically detects what is being loaded: If it is an archive it uses the archive.php file. If there isn’t one, it loads the default-header.php.

Novices to Carrington may think this a lot of work, that it leads to multiple files and the same amount of coding, it doesn’t and in cases where it does, it can be a good thing:

I find it leads to much less coding. Copy the default and add, delete or edit a line to do something. No need for conditional statements – Carrington takes care of that.

Usually all that is needed is to make one or two new files. It is unlikely one would want to have different actions for all page and post types.

Multiple files can help the developer modularise their work, much like OO programmers do. In addition, when an update to the framework is released from Crowd Favourite only the defaults will be overwritten at install – all the special coding the developer has done will be unaffected. Unless the default itself has been altered, which in a framework shouldn’t actually happen.

I am certain Carrington can be made do far more than Crowd Favourite say in the documentation or on their website. I’ll let you know how I get on with my experiments. (Hey, com’on – who hasn’t played with the bits in the Do not change the code above this line part?)

I predict Carrington will lead to the rollout of many more frameworks. That they become the standard system for delivering WordPress themes is likely too.

He called me recently for advice. One of those companies was now promising to get the website for his latest venture to position one, on page one, of Google for searches done for that type of business. (For a fee, of course).

What had him confused was they were talking about running two sites – the real one on the new venture’s domain (let’s call it www.newnew.ie) was up and running and another on their own domain (www.webweb.ie/NewNew) was ready to be released.

I read the mails they had sent him and took a good look at both sites.

Here is what they were doing:

• They claimed to have researched the new venture’s sector and determined a number of keywords.
• www.newnew.ie had 12 pages, with quite an amount of images and very concise text. www.webweb.ie/NewNew on the other hand was seen to have 60 pages, each having a considerably large amount of text.
• Each page on www.webweb.ie/NewNew was dedicated to one of the keywords.

This is termed keyword stuffing.

Google says “keyword stuffing” refers to the practice of loading a webpage with keywords in an attempt to manipulate a site’s ranking in Google’s search results. Filling pages with keywords results in a negative user experience …

For example, a page about rubber ducks might read something like “Welcome to our rubber ducks page. We sell all types of rubber ducks. Our rubber ducks are made of rubber and resemble real ducks. While yellow rubber ducks are very popular so too are red rubber ducks …”

Google are right about the negative user experience – face it, reading this would drive anyone insane!

Yahoo! concurs:

Some of what Yahoo! considers Unwanted:
- Pages built primarily for the search engines or pages with excessive or irrelevant keywords
- Pages that seem deceptive, fraudulent, or provide a poor user experience
- Pages using methods to artificially inflate search engine ranking

• There were no links from www.webweb.ie/NewNew to www.newnew.ie. However, the contact email address provided was for www.newnew.ie

So called doorway pages are large numbers of pages with repetitious or wordy content that contain many occurrences of a particular word or phrase. The intention is to attract users searching for that phrase then drive them toward a certain area on that site or another.

While this was not the case here it was similar in that the user’s enquiry and potential business would be driven to the newnew.ie email address and Newnew, the company, respectively.

Cloaking is a system whereby different content is served to users than to search engines. This is achieved by detecting who is requesting a page is and returning a set of content accordingly. For example, a user gets a Flash page while the search engine gets text.

Again, technically this was not the case here – search engines would see both sites – but the user would likely only discover one site.

I advised the client not to proceed. Such practices do more harm than good.

• Users finding the second site would get annoyed at the repetitious content and leave.
• Google and Yahoo! could discover the keyword stuffing and remove the second site from their indices.
• A competitor could report the site to the search engines and the same would happen.
• In the worst case scenario, the search engines could also blacklist the genuine site.

My personal golden rule for SEO is “cater for the user first and foremost – the search engines come second”. It is all well and good getting visitors to your site, but only quality content will keep them there.