Contented Management laughing buddha logo

Contented Management

Contented Management

Your website shall go the ball

Is yours a Cinderella website? Does it have an inner beauty that’s hidden away in some corner of the internet that potential Prince Charmings never visit? Does it suffer at the hands of a step-mother whose only interest is self-aggrandisement rather than nurturing their charge?

Get your website out of the scullery!

Promoting your web presence isn’t about just finding some kind of SEO godmother so you can trend on Twitter or make a splash on Google. You need to have content that’s stimulating, up-to-date and relevant to your target audience. If you simply tart up your presentation and wave it under people’s noses, your website will be about as popular as the ugly sisters.

So how do you get to the ball?

1. Make your content presentable.
Cleanse, freshen, and exfoliate! Remove anything that’s unsightly or redundant, accentuate your positive features by promoting them in your navigation and ensure that your design is focussed on your users’ needs.

2. Get out and network.
Once you have a website you think people will want to visit, you’ll need some kind of vehicle for getting your website in front of them. The channels that you use will depend on your target audience, but clearly SEO, social networking profiles and non-web media are all legitimate ways of getting yourself noticed. Unlike Cinderella’s pumpkin carriage, however, there needs to be honesty in the way you promote yourself. Habitat shot themselves in the foot recently by tagging their sales tweets with keywords about the Iranian election. Similarly if people are drawn to your website because it has popular but irrelevant keyword matches, they’re not going to hang around for long.

3. Keep that glass slipper.
Once you’ve got people to visit your site and experience your well-presented content, you need something to keep them coming back. RSS feeds are an obvious way of doing this, but you need to keep publishing good content if you want the party to carry on past midnight.

There’s not much point in having a website that’s an ugly sister – in your face but unattractive – or that’s beautiful but unknown. Every little website can grow up to be a princess if you can just show off its inner beauty.

Some further reading:

As a brief aside, did you know that Cinderella’s name comes from having her behind covered in cinders because she used to sit in the chimney to keep warm? And that her slippers were made from squirrel fur: vair in French, converted to verre (glass) by Charles Perrault to make the story more magical. Honest, guv’nor.

Philippe Parker on , | 26 June 2009

Contented Management

Basics of organising web content

There are a bewildering array of resources available on information architecture, user experience and interface design, so I just wanted to make a very quick post on how to approach the organisation of your web content.

  1. Identify key user types (personas)
  2. Identify key tasks they need to undertake (user journeys)
  3. Develop navigation to enable journeys (site maps)
  4. Develop user interface that will enable users to complete journeys (wire-frames)

Main advantages of doing things this way:

  • You’re not trying to fit in existing content unless it’s actually useful to your users.
  • You can identify content that’s missing easily.

There are more useful IA definitions at iaonesheeters.com

Philippe Parker on , , | 11 December 2008

Contented Management

Ajax: hero or zero?

As yet another vendor introduces AJAX to their WCM offering, it’s worth considering what benefits these interfaces bring you. Last year, Jonathan Downes and Joe Walker at CMS Watch provided a great introduction to the subject of Ajax in content management systems, but there are a couple of other points you should consider.

Firstly, in the last year or so, users have become much more familiar with these kinds of interfaces. Most webmail systems make use of the tool and there are countless portal-type sites and map applications that use JavaScript to create smoother browser-based interfaces. This should mean that people will be more comfortable with richer interfaces than with simple web forms.

Secondly, Downes and Walker tell us that Ajax generally equates to better performance. While the interface may give the end-user an impression of efficiency, this isn’t necessarily the case for the server. Remember that with each interaction, you’re sending a request — albeit small — to the server. Given that most CMS licences run on a per CPU basis and many environments have as a consequence been under-specified, introducing these tiny rapid requests could put some serious strain on your hardware and your budget.

These interfaces can be more user-friendly than some client software, but as with any CMS selection process you just need to be wary, size your environment appropriately and test with real editorial users to see if they get the desired usability benefits. It’s pretty safe to say that the smaller the number of users, the more benefit and least risk in deploying these kinds of tools.

A final word of caution: in the Iliad, Ajax was certainly mighty. But he was passed over by his peers for a hero with more guile and ended up destroying himself. Is this the sort of technology you want to unleash in your CMS campaign?

Philippe Parker on , , , | 14 October 2007