Manual Labor

Back when having a website was more important than having a sound business plan, Web content management systems were a must-have for large companies. IT managers bought into the idea that they needed an all-in-one system that would help them generate content, structure it, design it and publish it. But new research suggests these systems largely failed to live up to their promise. According to a recent report by Jupiter Research, 61 percent of companies that have deployed Web content management software still update their websites manually.

Surmacz, Jon. CIO Magazine (2003). Design>Content Management>Management>Web Design

MarthaStewart.com: Making the Case for Customer-Centric Content Management

When you hear the term "customer centric content management", you might think we're talking about marketing content. We're not. We're talking about managing the delivery of all types of content, including marketing content. And, we're specifically talking about providing individuals -- people -- both existing and prospective customers, with only the content that is relevant and of interest to them. You may think you already do a good job at this task, but in most organizations, there is significant room for improvement. Most of the problems are caused by one very big mistake: failing to listen.

Rockley Bulletin (2006). Design>Web Design>Content Management>User Centered Design

Moving to an XML-Based Web Site

In early 2007, I started the task of reworking the ageing HyperWrite Web site. The site was originally created in 1995. It underwent a major rework (to a frames-based design) in 1997, and was reworked in 1999, 2000 and 2002. In the decade since the Web site was launched, not only has Web technology moved on, but HyperWrite's activities, focus and business direction are now quite different. Time and budget were set aside to renovate the site to better serve HyperWrite's business needs, and to serve as a practical example of the company's capabilities.

Self, Tony. HyperWrite (2007). Articles>Web Design>Content Management>Case Studies

My CMS Ate My Search Engine Rankings

A dynamically-delivered site in and of itself need not denigrate your search engine rankings. Google and other spiders can follow dynamically-generated pages, up to a point. The key is to have links elsewhere on the site pointing specifically to those pages. If each page results from a purely dynamic query (e.g. using session variables), then you could be in trouble.

Byrne, Tony. CMSworks (2004). Articles>Web Design>Content Management>Search

Post-Implementation - Most Important

You would be forgiven for thinking that the lifespan of the typical usability project ends with final implementation and a product or website's release into the market. In one sense it does - the user-centred design process is over, and presumably the result is an easy-to-use product or site that is already yielding results. All well and good - but sometimes even the best interfaces cannot meet the changing requirements of the typical workplace. In this case, post-implementation user testing can pick up the difficulties that were not picked up first time around. At this point the client may quite rightly be wondering why these problems weren't spotted before deployment. The reason lies in the way in which the user has developed alongside the product. First impressions, whether favourable or not, may turn out to be misleading after an extended period of use.

Farrell, Tom. Frontend Infocentre (2000). Design>Content Management>Web Design

A Quiet Revolution in Website Maintenance

We're on the verge of a similar revolution in the area of website maintenance.

Bennaco (2005). Design>Web Design>Content Management

Rapid Web Development: How to Create Flexible Sites Quickly Using Standards Like CSS and XHTML

What do you do when you need to have a Web site done 'yesterday'? This article answers that question, showing you how to create sites quickly and flexibly using Web standards like cascading style sheets (CSS), structural HTML, and server-side includes. It contains examples that demonstrate how rapid Web development not only streamlines the process, but also makes updating easier.

Lewin, James. IBM (2001). Design>Content Management>Web Design

Rich Web Text Editing with Kupu

Kupu is an open source application, written in JavaScript, that implements a flexible, full-featured HTML editor that runs in a web page without any special plugins. Its primary use is as an embedded editor in content management systems (CMS), like Zope or Plone, where it allows users to create their own web pages. Its design is flexible enough so that you can embed it into pretty much any web application without too much difficulty.

Jones, Robert. O'Reilly and Associates (2005). Design>Web Design>Content Management>Plone

Seeking a More Dynamic Website

Putting content in a database will not inherently make your website more dynamic. Making sure that content providers keep information fresh, interesting, and relevant will make your website more dynamic -- and ultimately more useful.

Byrne, Tony. CMSworks (2004). Articles>Web Design>Content Management

Smarter Content Publishing: Building A Semantic Website to Increase the Efficiency and Usability of Publishing Systems

The web is not print. The need to create hypertext within pages requires more control over documents. Another is that web pages can also be applications, so access to the 'guts' of the page is needed to insert programming code. And ideally, we would like to separate presentation from content, enabling us to format the content in different ways for different purposes. How can we achieve all this with the efficiency and usability we've come to expect of other publishing tools?

Lombardi, Victor. Digital Web Magazine (2002). Design>Content Management>Web Design

Software for Building a Full-Featured Discipline-Based Web Portal

The University of Wisconsin-Madison's Internet Scout Project [1] received funding in the fall of 2000 from the Andrew W. Mellon Foundation [2] to build an open source software package that would allow collection developers to share their collection's metadata via the web. The resulting software, the Scout Portal Toolkit (SPT), is virtually turnkey, very inexpensive to maintain and operate, and easy for non-technical staff to download, set up and populate with metadata. Conforming to international standards for metadata, data harvesting, and Web technology makes SPT useful for and usable by a wide variety of projects and organizations, allowing and encouraging collaboration and record sharing among projects. Over the SPT project's two-year period, beta testers and in-house quality assurance testing provided valuable feedback, helping to ensure that the software was robust, easy to use, and well-suited to the needs of the intended audience.

Almasy, Edward, David Sleasman and Rachael Bower. D-Lib Magazine (2002). Articles>Web Design>Content Management>Software

Sources of CMS Uncertainty

Not all aspects of a content management system (CMS) project are equally easy. While some elements can be installed 'out of the box', others have proved difficult to implement. The starting point for improving the management of CMS projects is to recognise the sources of uncertainty, and how these affect project outcomes.

Robertson, James. Step Two (2004). Design>Web Design>Content Management

STC and the W3C  

As technologies like XML, content management software (CMS), and single sourcing continue to seep into technical communication, they bring demands for cost-effective development, faster time-to-market, and automation. Meeting these demands will require standards for coding, language, metadata, and other such elements. The good old days of 'winging it' in documentation are coming to an end.

Perlin, Neil E. Intercom (2004). Design>Web Design>Content Management>Standards

Web Two-Point Uh-Oh  

The problem with many Web 2.0 applications is the assumption that the community's motives are good, or at least neutral. Perlin's column explores how one of the drawbacks of Web 2.0--potential loss of control over information--has manifested itself.

Perlin, Neil E. Intercom (2007). Articles>Web Design>Community Building>Content Management

Website Automation: or, How I Saved My Sanity at the Last Minute

If there's one thing I can't stand, it's maintaining a website. The design is the fun part— solving problems, incorporating a brand, meeting user needs. That's what we live for. But maintenance? Yuck. So I surveyed the technologies available; what could I automate to ease the burden on myself and other volunteers? This article presents the results of this undertaking. It focuses mainly on the processes and their results. I discuss details of the tools and technologies where relevant, but this is not a tutorial on any tools or technologies; I'll provide resources for further information.

Hendry, Michael. MetroVoice (2002). Design>Web Design>Content Management

The WebWord Content Management System

The WebWord content management system is not technical, it is human. In fact, the technology is minimal and the web site works because a human understands and maintains the content using very simple tools. While this approach consumes a lot of time, it is simple and cost effective. Small and medium web sites can get along without using content management systems.

Rhodes, John S. WebWord (2001). Design>Content Management>Case Studies>Web Design

Webworks Publisher Tutorial: Better Jumps to Topic Titles  

By default Webworks Publisher uses file names and paragraph numbers as hyperlink targets, e. g. <a href='filename.html#55555'>. Most web browsers try to position the paragraph with the corresponding name anchor <a name='55555'> at the top of the screen if possible. If you jump to the top of a scrollable topic, any content above the title line (e.g. navigation graphics) is hidden. There are a few easy countermeasures.

Muller-Hillebrand, Michael. InFrame (2002). Design>Content Management>Web Design>Adobe FrameMaker

WebWorks Publisher Tutorial: Useful Meta Tags  

If you are using Webworks Publisher to create HTML pages which will be published for the WWW, you may want to place additional useful meta tags in your pages to be found and indexed by search engines and thus be found by interested persons.

Muller-Hillebrand, Michael. InFrame (2002). Design>Content Management>Web Design>Adobe FrameMaker

What is Wiki?

Wiki is a category of web server software that allows users to contribute content. Collaboration is the key to Wiki, which is designed as a powerful system for online communities to build web pages and web sites. Unlike blogs and forums, all users are allowed to contribute and edit existing content. Wiki is derived from the Hawaiian term "wiki wiki" meaning "quick". The concept behind a Wiki is that collaboration on projects will move it along quicker.

Small Business Software (2007). Articles>Content Management>Web Design>Wikis

Which Hosted Wiki Is Right for You?

A look at three hosted wiki services that are free or relatively cheap to use and provide easy tools to set up your wiki within minutes.

Nesbitt, Scott. InformIT (2006). Articles>Web Design>Content Management

Words Drive Action: An Interview with Gerry McGovern

Gerry McGovern is a world-renowned content-management expert and author of the books, 'Content Critical' and 'The Web Content Style Guide'. User Interface Engineering's Christine Perfetti and Josh Porter recently talked with Gerry about the importance of an editorial perspective in a web development process. Here is what Gerry had to say about his experiences.

Perfetti, Christine and Josh Porter. User Interface Engineering (2002). Articles>Content Management>Web Design

Integrating Social Media into a Web Content Strategy

Outside of the tech industry, skepticism and fear are the norm when it comes to social media. But it is simply about finding the best way to communicate with an audience. Social media consists of the same content already in use: text, audio, images, and video. The difference lies in its ability to open up new channels of communication.

Parrott, Britt. Digital Web Magazine (2008). Articles>Content Management>Web Design>Social Networking

Not All Content Needs to Be of Equal Quality

One of the greatest challenges confronting intranets is ensuring that content is up-to-date, accurate and useful. In many organisations, much thought and effort is put into maintaining (and enhancing) the quality of published content. What must be realised, however, is that not all content on an intranet needs to be of equal quality. Only once this is recognised can successful strategies be put in place to support content authoring and publishing.

Robertson, James. Step Two (2005). Articles>Content Management>Web Design>Intranets

Sixteen Steps to a Renewed Corporate Intranet

The growing status of content management systems (CMSs) is now providing many organisations with an impetus to revisit and renew their intranets. Unfortunately, while the technical aspects of implementing a CMS are well understood, many organisations are struggling to identify the issues with the content, structure and management of their intranets. The good news is that by following a disciplined approach, it is possible to re-invigorate an intranet, making it deliver real business benefits, and supporting strategic goals. This article outlines a sixteen step process which guides you through to a refreshed and dynamic new intranet.

Robertson, James. Step Two (2002). Articles>Web Design>Intranets>Content Management