We had a huge, unruly Web site. It just had different graphics, a better-named Web team and more people shoveling on content and applications. Finally, out of desperation, we decided to try a new-fangled thing called a Web content management system.
If a modern day Rip van Winkle woke up after just a year's sleep, he would be stunned by the buzz around Ajax today. Technology is moving very quickly in this space and whether you are a web author, a CMS developer, or a regular web user, Ajax will make some exciting changes to your world.
Many websites are still publishing content that is not core to their business. The justification is that such content will indirectly deliver benefit. This is not a good idea. Focus on the content that is directly applicable to your organization’s objectives. Any other content confuses. It wastes time and money.
The Santa Claus approach to content management creates a content management software wish list. It believes in the magic of technology to sweep away any and every problem. Typically, those who believe in Santa don't believe in defining their processes, or figuring out just why they need a website in the first place.
If content strategy isn’t in the current budget, though, how do you convince your client to add money for it? Your client might already realize content strategy can help create measurable ROI. If they don’t, help them understand. After all, relevant and informative content is what their audience wants; content strategy assesses the content they have and creates a plan for what they need and how they’ll get it.
Web site content must be recrudescent, repositorial, refluent, and rectilinear. What? Here's an innovative treatment of the essential attributes of online text. Find out why great web site content generally has these 14 characteristics that start with a "R".
Introduces the breadth of decision-making required in EPSS design. Explores choices and challenges facing designers in the design process, performance cycle, technology constraints, use of storytelling techniques, evaluation, and success factors.
The typical Web redesign results in a better looking more usable site where your information resources are easier to find. But so what? The typical Content Management System (CMS) implementation results in a more efficient process and better organized information. But so what? What does all that really get you? The sad fact is that very few people who install a CMS or redesign a site look beyond these simple justifications to the real reasons why they should organize information and create publications. It's not that these justifications are not important; it's that they are enablers of the more important justifications for managing and delivering content. The ultimate reason your organization manages information is the same reason your organization does any activity-to advance toward its goals. As obvious as this conclusion is, it amazes me how few CM and Web initiatives really address it. In this article, I'll outline one simple, powerful way you can go beyond the immediate efficiency and usability justifications to tie your CM inextricably to the foundations of your organization.
There are a wide variety of uses for Wikis and a level of interest in using them that’s matched by an extensive range of Wiki software. Wikis introduce to the Internet a collaborative model that not only allows, but explicitly encourages, broad and open participation. The idea that anyone can contribute reflects an assumption that both content quantity and quality will arise out of the ‘wisdom of the crowd.’
This paper describes the decisions by which the Association for Computing Machinery integrated good features from the Los Alamos e-print (physics) archive and from Cornell University's Networked Computer Science Technical Reference Library to form their own open, permanent, online “computing research repository” (CoRR). Submitted papers are not refereed and anyone can browse and extract CoRR material for free, so CoRR's eventual success could revolutionize computer science publishing. But several serious challenges remain: some journals forbid online preprints, the CoRR user interface is cumbersome, submissions are only self-indexed, (no professional library staff manages the archive) and long-term funding is uncertain.
People are looking for content to help them reach their goals, and you should start any site redevelopment by drawing up a content strategy designed to satisfy the user. We're currently doing this for a couple of our clients, and working through it ourselves now we've finally found the time to revamp our own presence (the cobbler's children and all that).
Designing and indeed front-end development for a website that will have content edited by non-technical users poses some problems over and above those you will encounter when developing a site where you have full control over the output mark-up. However, most clients these days want to be able to manage their own content, so most designers will find that some, if not all, of their designs end up as templates in some kind of CMS. By considering the CMS as you design, you can maintain far more control over the final output. If your designs will be implemented and integrated into the CMS by a developer, then taking control at the design phase will help you to keep control over the design as opposed to leaving decisions to the developer or the content editors.
A content inventory is a relatively straightforward process of clicking through your Web site and recording what you find. We’ve developed a simple Excel spreadsheet to help you structure your findings, and some tips on how to get through it.
Like it or not, large enterprises - the big name brands - have to work in structures and hierarchies that most E2.0 mavens ridicule but can’t come up with alternatives that make any sort of corporate sense. Therein lies the Big Lie. Enterprise 2.0 pre-supposes that you can upend hierarchies for the benefit of all. Yet none of that thinking has a credible use case you can generalize back to business types - except: knowledge based businesses such as legal, accounting, architects etc.
Summarizing recent CMS Watch research on portal software, Janus Boye finds that portal technology represents just the tip of the enterprise information iceberg. But given the diversity of portal scenarios, you should ask yourself which iceberg you're on.
On of the frustrating things at Enterprise 2.0 Conference this go around was there are still myth mantras that echo the podiums and halls. They really need to stop as they have never been proven to be right and are often proven to be incorrect (many times shown to be wildly incorrect).
Here’s the cool thing about content strategy. It doesn’t just tell you what content should go on your site, but it answers a whole bunch of other important questions.
There are some that would like to dump the “intranet” name, as it’s associated with the “old” vision of intranets as a publishing platform, a dumping group for documents, and a place for the CEO to post his thoughts. This narrow vision of the intranet must certainly die. In the process, intranet teams need to go from being custodians of an internal website, to facilitators for business improvements. In many ways, the word “intranet” has too much baggage, and is an anchor for much-needed changes.
This paper advocates an often-neglected search-support technique, approximate or 'fuzzy' matching of user search terms. When properly deployed, fuzzy matching can significantly enhance the benefits of other, more common approaches to end-user answer retrieval from online reference collections. We compare crude with more sophisticated approximation techniques to explain how astute fuzzy-match software can convert many different near-miss situations (such as those involving faulty prefixes or suffixes, character misplacement, nonstandard word stems, or unanticipated redescription of concepts) into more adequate results. We also suggest practical ways to overcome fuzzy matching's own major drawbacks (namely, problems with search speed, search imprecision, and misinterpretation of search results). The resulting analysis clarifies how to deploy fuzzy matching for maximum effectiveness. We conclude that appropriate fuzzy matching enables more frequent, more flexible search success than do ordinary retrieval-improvement techniques used without it.
This paper describes the Electronic Resource Library (ERL) at http://plutonium-erl.actx.edu. This is a web-based, subject-oriented digital library on the topic of plutonium and its ancillary disciplines. Previous research analyzing differences in the information-seeking behavior of scientists and engineers is reviewed and lessons learned applied to this digital library model. Special consideration has been given to recommendations in the SATCOM report from the National Academy of Sciences/National Academy of Engineering Committee on Scientific and Technical Communication. This report strongly advocated the development of “specialized need-groupservices” to support the work of the engineer and practitioner.
When you transfer WordPress from one web host to another, you have to go through quite a few steps, especially if your current web host owns the domain name. Transferring the domain name is the biggest hassle, because it requires a handful of special codes and verifications, but just understanding what’s involved in a site transfer can be somewhat overwhelming. I just helped a person, so I’ll briefly outline the steps below in case you’re thinking of moving to a new web host.