We spend a lot of time considering the technology of a particular site, customers are always keen to point out the fact that they ‘need’ features and functions to make their site ‘useful’ and attract users, plans involve the development and design of forums, blogs and web 2.0 features that are a must for the new site that will move them into the 21st century, and then as a by line there is content …
I forwarded an article from giraffe forums, which was later twittered to the community regarding the importance of content in the procurement of a CMS for any organisation. it suggested that migration of old content into a new CMS and web design, with the added function and features that a new system offers, but the same content, will effectively achieve nothing,
Content makes a site.
It should be thoughtfully written with the reader in mind and use language that they can will understand, use common language, and avoid industry acronyms.
It should be long enough to inform the reader, but not so long that they don’t want to read the piece. Add a ‘contact us’ link so that the reader can get in touch should they need more information.
Structure the content in a sympathetic manner, the reader dies not know your companies internal structure and probably doesn’t care, structure content in way that the reader will expect.
In a recent thread on the information architects institute mail list, the procurement of a CMS was again the subject of discussion, in this thread, one contributor suggested that the IA focus on the ‘Goals’ of the CMS rather than the features, again positioning the procurement away from the technology and more towards the desired effect.
Informing the user, allowing them to interact with the content and thus the organisation,
Web2.0 is about user generated content not technology, so don’t muddy the waters with unnecessary features, moderate them to the user, what they need and how they expect to be able to interact with you.