http://tc.eserver.org/dir/Design/Content-Management A listing of the most recently indexed works about Design and Content Management in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Design/Content-Management http://tc.eserver.org/35770.html http://tc.eserver.org/35770.html SharePoint can neither create nor destroy organizational chaos, but does an excellent job of reflecting the level of organizational chaos that existed at the time of deployment. The “SharePoint paradox” and paths to SharePoint wickedness. The power of Issue Mapping and IBIS based collaboration. How to leverage the best of SharePoint and Issue Mapping. http://tc.eserver.org/35772.html http://tc.eserver.org/35772.html Given the pressures on firms to provide increased value at lower costs, it’s imperative that they find ways to reduce the costs of creating and managing documents and increase their value to clients and personnel. Microsoft SharePoint provides a range of features to make your firm’s documents “smarter,” from capturing rich metadata to automating workflows to intelligent search. As applied, these features can transform passive documents into active, reusable resources. In this article I’ll describe some of the ways that SharePoint can reduce the effort to create, manage and retrieve documents and increase their value, as smart documents, to both your firm and its clients. http://tc.eserver.org/35773.html http://tc.eserver.org/35773.html The SharePoint 2010 Managed Metadata feature has been my favourite topic since coming back from the SharePoint conference. I get excited about this kind of thing because metadata is a big part of all of the software we build. But some people are probably saying "Why should we get so excited about new metadata features in SharePoint? The new UI and improved capacity are really the neat things about SharePoint 2010." http://tc.eserver.org/35677.html http://tc.eserver.org/35677.html The shift in information development from a narrative to a modular writing style reflects the established shift towards modularization of source code. What can information developers learn from software developers? What are the challenges and benefits of the modular approach? http://tc.eserver.org/35333.html http://tc.eserver.org/35333.html How closely does the content in your CMS resemble the logical content you planned on? # Different systems have vastly different content modeling. http://tc.eserver.org/35310.html http://tc.eserver.org/35310.html Intelligent content is content which is not limited to one purpose, technology or output. It’s content that is structurally rich and semantically aware, and is therefore discoverable, reusable, reconfigurable and adaptable. It’s content that helps you and your customers get the job done, often automatically. http://tc.eserver.org/35297.html http://tc.eserver.org/35297.html A Content Curator is someone who continually finds, groups, organizes and shares the best and most relevant content on a specific issue online. I think that professional writers and technical writers should consider a move towards this role. We already search for and find the best content, sift through loads of content, discard poor content, and publish the most worthy content whenever a software release goes out. This description also sounds like something a content strategist would do as part of their analysis of the content. http://tc.eserver.org/35298.html http://tc.eserver.org/35298.html A Content Curator is someone who continually finds, groups, organizes and shares the best and most relevant content on a specific issue online. The most important component of this job is the word "continually." In the real time world of the Internet, this is critical. In an attempt to offer more of a vision for someone who might fill this role, here is my crack at a short manifesto for someone who might take on this job. http://tc.eserver.org/35287.html http://tc.eserver.org/35287.html Over the past couple of weeks I’ve had the chance to experiment with WebWorks ePublisher, a set of tools that converts documents from Word, FrameMaker and DITA XML to a number of different output formats. One of those output formats is Confluence wiki. It’s been very interesting, so I thought I’d blog about it and see if anyone else wants to give it a go as well. http://tc.eserver.org/35170.html http://tc.eserver.org/35170.html 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. http://tc.eserver.org/35122.html http://tc.eserver.org/35122.html Although managing costs is important anytime, it is especially important in today's economic reality where budgets are shrinking drastically. Getting your money's worth as well as what you need to support your data should be a core factor of any data project. The two biggest cost factors are the type of conversion work you need done and how much of it you'll need. This article focuses on how your goals for your project relate to the output format you choose, and how that format impacts costs. While some outputs, like XML, provide higher capabilities, they also cost more to create. http://tc.eserver.org/35123.html http://tc.eserver.org/35123.html While I'm a big fan of XML for many purposes, it's a misconception that it's the single best solution in every scenario, and it's worthwhile to consider the alternatives in situations where the benefits of XML are not necessary. In this article, I discuss alternatives to XML, SGML, and HTML that might be suitable when budgets are more limited. While XML is perfect for highly coded information, other options can work well for many kinds of information. Markup languages are at the high end of the cost spectrum, so if you don't need the benefits they provide, you certainly should consider the alternatives discussed below. http://tc.eserver.org/35093.html http://tc.eserver.org/35093.html While the design of democracy is a wonderful thing, democratic design is less positive. We’ve heard over and over that “everyone is a designer,” and that through a combination of user-generated content, ubiquity of access, and new tools, design has finally made its way out of an ivory tower and into the grasp of the masses. What, exactly, have the masses gotten their grubby paws into? Can one truly claim to be a designer when they upload a picture to Facebook or remix a video for YouTube? http://tc.eserver.org/35030.html http://tc.eserver.org/35030.html Usually, the one thing missing from the planning of a WCM-driven web site is what's most likely to shoot the implementation in the foot: the functional design of the CMS back-end. The form and function of how the CMS will work, look and feel for the end-user of the system, not the visitor to the web site, is too often overlooked. This is odd: isn't the rationale for getting a CMS in the first place usually based on some kind of ROI in efficiency in actually producing the content and sites? http://tc.eserver.org/35033.html http://tc.eserver.org/35033.html Web Managers must think globally (information) and act locally (Web) all the while trying to widen your universe and build the internal business relationships which will allow your organization to manage its information more holistically now or in the future. http://tc.eserver.org/34907.html http://tc.eserver.org/34907.html オンラインコンテンツは、文脈とは無関係にユーザーの目にとまることが多い。本来想定された目的とは違う目的で読まれることもよくある。そうした目的を全部予測することはできないが、テキストのさまざまな利用を考慮することはできる。 http://tc.eserver.org/34715.html http://tc.eserver.org/34715.html Technical Communication continues to change as we find new ways to meet the needs of our audiences. I have attended several conferences recently and discussed several of the latest trends with other technical communicators. This article provides a quick list of several of these trends and ideas. http://tc.eserver.org/34694.html http://tc.eserver.org/34694.html SEO techniques will increase your search rankings and SEM will get you traffic on the top search engines. But a boatload of quality content will also accomplish these things and prepare you for the more contextual future of search. http://tc.eserver.org/34678.html http://tc.eserver.org/34678.html “Content types” are among the least understood, and yet most potent, aspects of user experience and web design. Most people encounter them for the first time when implementing a grand-scale content management system (CMS) because you have to define content types before building templates for each kind of content you’re going to publish. Because they associate content types so closely with CMS, some make the mistake of equating content strategy with content management. They’re not the same thing, though they are certainly related. Your content strategy specifies the content types that will then be modeled for your CMS. http://tc.eserver.org/34679.html http://tc.eserver.org/34679.html Be known for your content first, for your name second. I can’t bear to hear anyone say one more time that “content is king,” but the truth is simple, if painful. http://tc.eserver.org/34576.html http://tc.eserver.org/34576.html There are two camps in technical documentation. There’s the “quick web” folks who connect easily and author easily, and then there’s the “structured quality” camp that requires more thoughtful testing and time spent on task analysis and information architecture. http://tc.eserver.org/34487.html http://tc.eserver.org/34487.html The goal was to use Subversion (SVN) as a poor man's CMS, and take advantage of great PC-based editors like DreamWeaver (for HTML) and XMetaL (for DITA). Eventually, we could add pre-commit checks and utilities to give us some of the advanced functionality we'd really like--like link management and metadata change management--but in the meantime we could do everything manually to get by. All we had to do was install Subversion and enable the WebDAV interface in Apache. But many hurdles later, I'm exhausted from jumping over them. Every one requires me to look through 20 web pages in search of a solution, and each time I surmount one obstacle, it's only to find a new one standing in my way. http://tc.eserver.org/34493.html http://tc.eserver.org/34493.html So what's wrong with using <b>, <i>, and <tt>, anyway? What's so useful about identifying things as menu items, APIs, or filenames? Here's the list of reasons that surfaced at the recent 2008 DITA/CMS Conference. What are your thoughts? http://tc.eserver.org/34455.html http://tc.eserver.org/34455.html We still 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. http://tc.eserver.org/34399.html http://tc.eserver.org/34399.html 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.’ http://tc.eserver.org/34295.html http://tc.eserver.org/34295.html Users often see online content out of context and read it with different goals than you envisioned. While you can't predict all such goals, you can plan for multiple uses of your text. http://tc.eserver.org/34312.html http://tc.eserver.org/34312.html Unless you’re a one person web shop with no team to collaborate with, you’ve experienced the frustration that goes along with file sharing. No matter how hard you try, when multiple people are working on a single project without a version control system in place things get chaotic. In this article, I’ll give you a quick review of Git, an excellent version control system. http://tc.eserver.org/34313.html http://tc.eserver.org/34313.html Git, though remarkably handy and powerful, is also remarkably hard to use sometimes. Though you can learn the basics easily enough, it can be really tough to dig yourself out of certain corners if you don’t understand what’s going on under the covers. This page provides links to documents, how-tos, cheat sheets, tips, and tricks related to learning and using git. http://tc.eserver.org/34220.html http://tc.eserver.org/34220.html With the number of publicly offered Web service APIs, it's now much easier to get content from different Web sources and to build mashups—if you have access to the right APIs and tools. Discover how you can combine an obscure cross-domain call technique (JSONP) and a flexible JavaScript library (jQuery) to build powerful mashups surprisingly quickly. http://tc.eserver.org/34118.html http://tc.eserver.org/34118.html If you cater to the younger group, you risk alienating your most senior people (talented, expensive, hard-to-replace experts; people you don't want to lose to the competition; people with great political capital in the organization, who can perhaps defeat an IT initiative by pushing back hard). On the other hand, if you cater to the older group, you risk alienating the younger workers; and you risk keeping obsolete systems in place far longer than you should, making future replacement that much more difficult while also impeding business objectives, etc. http://tc.eserver.org/34095.html http://tc.eserver.org/34095.html There’s one area that I believe user experience has lagged behind: the enterprise software space. I can’t tell you how many frustratingly unusable enterprise Web applications I’ve encountered during my 12 plus years in corporate America. As important as the user experience of enterprise software is to a business’s success, why isn’t its assessment usually a factor in technology selection? http://tc.eserver.org/34096.html http://tc.eserver.org/34096.html In this column, I’ll provide a technology selection framework that can help enterprises better assess the usability and appropriateness of enterprise applications they’re considering purchasing, with the goal of ensuring their IT (Information Technology) investments deliver fully on their value propositions. http://tc.eserver.org/34010.html http://tc.eserver.org/34010.html Much in the same way that Microsoft Word and PageMaker made desktop publishing more widely available and eliminated the need for tagging to achieve formatting, blogs and wikis are doing the same for the web. You can use WordPress to create an entire web site without knowing or using HTML. Editme.com is providing web site services using wiki technologies. These tools help users publish content with less knowledge of the underlying tagging. http://tc.eserver.org/33913.html http://tc.eserver.org/33913.html This paper shows how topic maps can address the limitations of traditional content management systems while building on their strengths. The term ITMS (Integrated Topic Management System) is coined for a content management system based on topic maps, and the paper shows what is necessary to build such systems, as well as what benefits they bring. The use of the WebDAV protocol to layer topic maps over content stores is also considered, and an abstract topic map-to-content store protocol is sketched, which corresponds very closely to WebDAV. http://tc.eserver.org/33914.html http://tc.eserver.org/33914.html Topic maps are a new ISO standard for describing knowledge structures and associating them with information resources. As such they constitute an enabling technology for knowledge management. Dubbed “the GPS of the information universe”, topic maps are also destined to provide powerful new ways of navigating large and interconnected corpora. While it is possible to represent immensely complex structures using topic maps, the basic concepts of the model — Topics, Associations, and Occurrences (TAO) — are easily grasped. This paper provides a non-technical introduction to these and other concepts (the IFS and BUTS of topic maps), relating them to things that are familiar to all of us from the realms of publishing and information management, and attempting to convey some idea of the uses to which topic maps will be put in the future. http://tc.eserver.org/33869.html http://tc.eserver.org/33869.html This week I caught up with Debbie Campbell, a Colorado web designer and developer and the owner of Red Kite Creative, and asked her about the latest trends in web design. I’ve been following Debbie on Twitter for a while. This week she posted a few tweets about web design and WordPress, so I asked her to share a little more. http://tc.eserver.org/33842.html http://tc.eserver.org/33842.html CMS is revolutionizing the way higher education handle online content. So why are most universities still managing their course catalogs by hand? Join David Cummings for an in-depth look at how XML can improve a university beyond its website. http://tc.eserver.org/33771.html http://tc.eserver.org/33771.html OK. So you have your documents in XML. How do you deliver them to readers? You've heard great things about separation of form and content, and would like different kinds of readers to see the documents styled in different ways. And in order to make the collection of documents more useful, you would like to have full-text search. The quality assurance people would like some help with tools for checking documents and finding errors and inconsistencies in existing ones. Oh, and by the way, we just took a budget cut, so can you do it without breaking the bank? http://tc.eserver.org/33654.html http://tc.eserver.org/33654.html Business integration is at the heart of many of today's industry trends. As businesses consolidate infrastructure, and look at rolling out service-oriented architectures, they are finding they need to link previously isolated applications. It's not easy. You can't link applications without some form of middleware, an extra application layer that lets their various systems communicate. Whether you use web services, or a message-based solution, there's one key feature that's at the heart of modern integration technologies: XML. http://tc.eserver.org/33568.html http://tc.eserver.org/33568.html John Willis recently published a post that equates social publishing with social networking. While the post is pretty good, and I agree with most of the points, I need to correct the bit about the definition of social publishing. It’s way more than social networking. Let me explain. http://tc.eserver.org/33258.html http://tc.eserver.org/33258.html 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. http://tc.eserver.org/33259.html http://tc.eserver.org/33259.html 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. http://tc.eserver.org/33262.html http://tc.eserver.org/33262.html 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). http://tc.eserver.org/33263.html http://tc.eserver.org/33263.html 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. http://tc.eserver.org/33264.html http://tc.eserver.org/33264.html There are two types of people involved in websites today: those who see content as an asset, and those who see it as a commodity. The latter better start looking for a new career. http://tc.eserver.org/33266.html http://tc.eserver.org/33266.html What's really important to measure for your website? Firstly, you need to measure how successful you are at creating, editing and publishing content. These are your web content management processes. Secondly, you need to measure reader behavior. There will also be some core website performance issues to measure. This week, I'd like to examine key web content management process measurables. http://tc.eserver.org/33267.html http://tc.eserver.org/33267.html Are the people who have least to say in your organization publishing most on your intranet or public website? Are the people who have most to say publishing least? You're not alone. Organizations are slowly realizing that managing a website is as much about what you don't publish as what you do. http://tc.eserver.org/33269.html http://tc.eserver.org/33269.html Large websites often struggle to develop an efficient and cost-effective publishing model. Centralizing publishing ensures a consistent quality of what is published, but is often slow and frustrating. Decentralized publishing is faster and often more cost-effective, but can result in inconsistent quality, unless rigorous publishing standards are adhered to. http://tc.eserver.org/33272.html http://tc.eserver.org/33272.html You take a content inventory because, before redesigning a website or intranet, you need to know what you have. This is especially important if you will be migrating your content to a new structure or new CMS - at some point you need to know every single content element. http://tc.eserver.org/33273.html http://tc.eserver.org/33273.html There is a lot of mumbo-jumbo like the word "taxonomy" that is being thrown around to describe how to manage so-called unstructured content like business documents, web site pages, and old fashioned technical reports and articles. On the one hand, we want to remember what we already know about how to create a useful core catalog record to describe a content object so it can be found again later when needed. On the other hand, there are some bad habits and obsolete ideas like inverted file indexes that we need to get beyond. This talk is about what we have seen in dozens of applied information management projects over the past few years, and how you can take advantage of what you already know to solve big problems like these in your own organizations. http://tc.eserver.org/33278.html http://tc.eserver.org/33278.html Personalization hasn't worked because most people don't have a compelling reason to personalize. It hasn't worked because the cost of doing it well usually significantly outweighs the benefits it delivers. It hasn't worked because managers have seen it as some Holy Grail of content management. http://tc.eserver.org/33282.html http://tc.eserver.org/33282.html Information technology has become the Trojan Horse of information overload. It has been invited into the organization as some magical gift that will bring greater efficiency and reduced cost. Once inside, it feeds on resources and spews out unimaginable quantities of low quality data. Information technology has become the problem. The solution is to invest in people again. http://tc.eserver.org/33284.html http://tc.eserver.org/33284.html Content management systems suck. Or so you would think from the strife heard from analysts and practitioners alike. And yet, many websites regularly publish vast amounts of information with superior control and ease compared to manually editing pages. So where’s the disconnect between what’s possible and the too-often failure of CMS? http://tc.eserver.org/33086.html http://tc.eserver.org/33086.html 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. http://tc.eserver.org/33094.html http://tc.eserver.org/33094.html 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. http://tc.eserver.org/33100.html http://tc.eserver.org/33100.html The intranet is beginning to restructure the organization in more ways than one. Content is now an asset, and the people who manage it need to treat it as such. Managing editors, and their team, understand how technology can facilitate effective publishing, collaboration and self-service focused application development. http://tc.eserver.org/33101.html http://tc.eserver.org/33101.html There is a view in some organizations that an intranet is only for staff, so you can publish what you want. Quality content matters as much on an intranet as on a public website. Get your content right to begin with. Keep it right by removing out-of-date content. http://tc.eserver.org/32714.html http://tc.eserver.org/32714.html The net effect of social networking is the increasing availability of fine-grained information about locales. This information is both interesting and valuable. It is sought after by people living in these places and by advertisers who are trying to reach these people. A handful of startups are recognizing the big potential of local information - relevance. In this post we look at different aspects of the hyperlocality, from satellites to local blogs, and ponder how this information will be organized and monetized. http://tc.eserver.org/32644.html http://tc.eserver.org/32644.html 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. http://tc.eserver.org/31840.html http://tc.eserver.org/31840.html A case study of a team approach to information architecture at Duke University by graduates of the Duke Continuing Studies Technical Communication Certificate program. http://tc.eserver.org/31753.html http://tc.eserver.org/31753.html What distinguishes the underlying strategies of Adobe InDesign from QuarkXPress is the absence or presence of a content management system (CMS). And each company asserts that it’s following the less-traveled road. The problem is they’re both taking roads most traveled because of their respective stances towards integrated content management systems, and I’ll show you how after looking at their respective strategies. http://tc.eserver.org/31352.html http://tc.eserver.org/31352.html What would you do if you had to develop and deliver personalized training to 900,000 employees, located in 34,000 different locations globally with a complex set of variables that changes training on a location-by-location basis? The key is reusability 2.0. While technology-delivered training has become mainstream in many organizations, most are still not fully leveraging the power of reusable learning content to meet their instructional needs. http://tc.eserver.org/31141.html http://tc.eserver.org/31141.html In all companies, the requirements of an editorial system are worked out individually from the analysis of existing functioning and the definition of editorial and publication processes required in the future. The first important criteria for analysis are change frequencies and degree of reuse of the published information. The description of the information types as well as translation sequences constitute another starting point for the definition of a modular work process (single-source principle) and publication options (cross-media publishing). http://tc.eserver.org/30771.html http://tc.eserver.org/30771.html Every web site is conceived and designed keeping in view a particular purpose to serve. The aim of web site may vary: some web site intends to showcase products or services of the company it belongs to, some provides information to its target audience, or some just exposes its company on the web in a brand building exercise. This is to note that whatever be the nature of web site, web copy plays it own crucial role in furthering the interest of the site. It is imperative that web content is easy-to-read, easy-to-find, and easy-to-understand. http://tc.eserver.org/30685.html http://tc.eserver.org/30685.html Behind all the questions about how to model something is a bigger question: do you model it at all? When is it obvious to structure some content, and when do you just throw it into the 'WYSIWYG pile'? http://tc.eserver.org/30604.html http://tc.eserver.org/30604.html This document assesses WordPress 2.01 against the Authoring Tool Accessibility Guidelines 1.0. http://tc.eserver.org/30269.html http://tc.eserver.org/30269.html Automated templates are an alternative to traditional supporting information for helping users perform complex tasks. In this study users performed tasks with and without wizard to trial and error, printed manuals, and online the use of automated templates. Results suggest that if fakes help, and examined the use of supporting information some time for users to learn to use automated templates, but in performing complex tasks. We also considered once they do, the templates help users perform tasks more whether automated templates serve an educational successfully and more quickly. http://tc.eserver.org/30258.html http://tc.eserver.org/30258.html Organizations today face the challenge of two important enterprise architecture requirements: the need for agility and the overhead of regulatory governance. These requirements can be seen as mutually antagonistic -- if business processes must be flexible, then governance of those processes may be difficult. This article, part six in a six-part series, explores the notion of using manageability as a key enterprise architecture (EA) quality attribute to solve this problem. EA development is an ongoing process, and the central idea of this article is that by applying manageability as an EA attribute, the organizational processes, systems, and software become manageable. http://tc.eserver.org/30199.html http://tc.eserver.org/30199.html The single most important factor in a successful CMS implementation lies with you and your people. Your staff members are the principal users of the system, and the SMEs in your organization are the secondary users. It is their adoption of the new processes and governance structures that makes or breaks a CMS implementation. According to some, process and cultural change accounts for 90%, while technology contributes only 10% to the success of a CMS. http://tc.eserver.org/30121.html http://tc.eserver.org/30121.html 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. http://tc.eserver.org/29995.html http://tc.eserver.org/29995.html We hear the term knowledge management bandied about. It sounds suspiciously like a trendy new phrase for what we used to call 'documentation.' In truth, knowledge management is more than documentation. It encompasses documentation, data management, library management, and information design. Knowledge management is increasingly important; as the amount of content has increased, the task of locating the information in the content has become more difficult. You see, information is different from content. And knowledge is something that derives from information. http://tc.eserver.org/29973.html http://tc.eserver.org/29973.html 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. http://tc.eserver.org/29913.html http://tc.eserver.org/29913.html Information models are a critical component of single sourcing, enterprise content management, and dynamic content management. The information model is your blueprint for the effective writing, structuring, and delivery of reusable content. This session explains how to design information models, including information product models and element models. It also explains the role of metadata and how to effectively design it. http://tc.eserver.org/29742.html http://tc.eserver.org/29742.html A weblog or 'blog' is a Web site with content consisting of a series of discrete postings added sequentially and presented in reverse chronological order. Historically used for personal Web sites, blogs in fact represent a form of lightweight content management that can be adapted to virtually any topic, including technical communication. The recent explosion of blogs is in part a result of the availability of publishing tools that simplify their creation. These tools vary significantly in capability, setup, and ease of use, and each offers advantages and disadvantages. http://tc.eserver.org/29544.html http://tc.eserver.org/29544.html 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. http://tc.eserver.org/29397.html http://tc.eserver.org/29397.html Cisco Systems recognizes a need to move from creating and delivering large inflexible training courses, to database driven objects that can be reused, searched, and modified independent of their delivery media. This effort is called the Reusable Information Object Strategy. This strategy defines the standards and process for designing and developing Reusable Information Objects (RIOs) at Cisco Systems. http://tc.eserver.org/28946.html http://tc.eserver.org/28946.html 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. http://tc.eserver.org/28933.html http://tc.eserver.org/28933.html Content Management Systems promise so much: content is easier to publish, easier to update, and easier to find and use. Lots of promises, but do CMSs really deliver? Masood Nasser examines why Content Management Systems often fail and shows how Information Architecture can come to the rescue. http://tc.eserver.org/28562.html http://tc.eserver.org/28562.html As other areas within organizations begin to consider structured content for the same reasons as technical communication departments, technical communicators have a golden opportunity to assist others in their move toward structured CM. http://tc.eserver.org/28306.html http://tc.eserver.org/28306.html 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. http://tc.eserver.org/28184.html http://tc.eserver.org/28184.html A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let's explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents. http://tc.eserver.org/28131.html http://tc.eserver.org/28131.html 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. http://tc.eserver.org/27853.html http://tc.eserver.org/27853.html Most web-based content management systems offer a variety of tools to help contributors enter text. When it comes to graphics, content contributors are usually expected to provide web-ready images to the system. This means that either editorial users needs to know about image optimisation and web image formats, or additional staff are required to make web-ready images out of raw materials. This article demonstrates a technical solution to this problem. http://tc.eserver.org/27044.html http://tc.eserver.org/27044.html 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. http://tc.eserver.org/26742.html http://tc.eserver.org/26742.html Almost one-third of the users reported that more than 40 percent of the storage spending is for unstructured documents and information--I think that percentage will continue to grow annually. Further, AIIM President John Mancini, who prepared the report, found that larger organizations especially are aggressively pursuing consolidation and rationalization of their storage and archiving strategies--but that cost is not the prime motivation behind those activities. http://tc.eserver.org/25981.html http://tc.eserver.org/25981.html This white paper discusses the role of an XML repository into today’s enterprise infrastructure. Virtually every database and repository provide some degree of XML support; however, there are important distinctions between support for XML as a data type and the role of a repository whose architecture and operations are optimized to support the broad family of XML recommendations and standards. Specifically, this white paper will explore: The nature and extent of XML use across the enterprise, cost and quality of service implications of an infrastructure with, and without, an XML repository, the evolution of XML repositories from both a technology and a market segment perspective, criteria to determine when an XML repository would add significant value to an existing infrastructure, and capability and packaging recommendations for XML repository functionality that can be used to evaluate specific offerings. http://tc.eserver.org/25941.html http://tc.eserver.org/25941.html If you're thinking about getting, or updating, a website, chances are that you'll run into a web designer who will try to sell you on the idea of a 'dynamic site.' Here's what you need to know in order to decide if such an approach is for you. http://tc.eserver.org/25934.html http://tc.eserver.org/25934.html We're on the verge of a similar revolution in the area of website maintenance. http://tc.eserver.org/25755.html http://tc.eserver.org/25755.html Content management systems are key to running an efficient website. Keep the development group out of the loop on updating content, and you will move ever so much faster. 'Content' doesn’t need the same kind of source control that scripts and templates need. Specific design suggestions follow. http://tc.eserver.org/25562.html http://tc.eserver.org/25562.html The O'Reilly Radar blog will track what we're tracking, and turn the blips into conversations. http://tc.eserver.org/25567.html http://tc.eserver.org/25567.html 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. http://tc.eserver.org/25064.html http://tc.eserver.org/25064.html 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". http://tc.eserver.org/24626.html http://tc.eserver.org/24626.html While you can create very powerful content management solutions with most open-source packages -- they have a much steeper learning curve than you experienced with HTML or Flash. http://tc.eserver.org/24620.html http://tc.eserver.org/24620.html 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. http://tc.eserver.org/24625.html http://tc.eserver.org/24625.html 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. http://tc.eserver.org/24199.html http://tc.eserver.org/24199.html 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. http://tc.eserver.org/23992.html http://tc.eserver.org/23992.html Few organizations have seen much good come of content-management BPR initiatives so far. Of the many reasons for these failures, one stands out: these BPR initiatives—and the systems they spawn—are focused on realizing organizational objectives without sufficient regard for the context, habits, and goals of the people who will actually use the system. http://tc.eserver.org/23818.html http://tc.eserver.org/23818.html Many technology companies, consultants, and academics are hyping the future of Web services. But how will this background transfer of data between applications affect the user experience? http://tc.eserver.org/23695.html http://tc.eserver.org/23695.html 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. http://tc.eserver.org/23636.html http://tc.eserver.org/23636.html When people think about content management, they generally think about it from a systems perspective, focusing primarily on tools and technology. While it is true that content management usually requires a technological solution, it also requires that content be designed for reuse, retrieval, and delivery to meet your authors' and customers' needs. Content management requires that tools be configured to support authoring, reviewing, and publishing tasks, but first, those tasks must be designed. Designing content and the processes to create, review, and publish it is what information architecture is all about. The Information Architecture section of The Rockley Report will focus on the different aspects of information architecture for content management. This article introduces you to some of the components of information architecture that we will cover in The Rockley Report over time. http://tc.eserver.org/23135.html http://tc.eserver.org/23135.html How to extract content from a portion of a PDF document. http://tc.eserver.org/23056.html http://tc.eserver.org/23056.html A well-designed information architecture with intuitive organization, labeling, navigation, and indexing systems can significantly reduce the amount of time that users spend blundering through the hierarchies of Web sites and intranets. How much is this time-savings worth? The case is clearest for intranets where the users are your employees. http://tc.eserver.org/22648.html http://tc.eserver.org/22648.html In this White Paper, we examine the benefits of automated content management, and demonstrate where efficiencies can be gained within your organization. Web sites with more than a few information pages may benefit from content management systems (CMS). Content management systems are automated tools that allow for web site content to be created and administered on a recurring basis. The result puts the responsibility for content development into the hands of the authors (where it belongs) and out of the hands of the programmers. http://tc.eserver.org/22443.html http://tc.eserver.org/22443.html CMS Wiki is a knowledge base for Content Management. http://tc.eserver.org/22441.html http://tc.eserver.org/22441.html Content management is information architecture writ large. http://tc.eserver.org/22414.html http://tc.eserver.org/22414.html The process of content management begins when an organization comes to the realization that it needs a system to manage content. While the interpretation of the term content management (CM) can be as simple as a set of guidelines for organizing and maintaining content, more typically today it means a sophisticated software-based system. A full-featured content management system (CMS) takes content from inception to publication and does so in a way that provides for maximum content accessibility and reuse and easy, timely, accurate maintenance of the content base. http://tc.eserver.org/22086.html http://tc.eserver.org/22086.html 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. http://tc.eserver.org/21748.html http://tc.eserver.org/21748.html Content management systems suck. Or so you would think from the strife heard from analysts and practitioners alike. And yet, many websites regularly publish vast amounts of information with superior control and ease compared to manually editing pages. http://tc.eserver.org/21103.html http://tc.eserver.org/21103.html Greymatter is an excellent web content management system. After you install it, you can begin to syndicate your content using XML. This article gives you an explicit step-by-step overview of how I created RSS 1.0 and RSS 0.92 files using Greymatter. It is assumed that you have some knowledge of HTML and XML, and that you have already installed Greymatter. Many examples and references are provided to help you along the way. http://tc.eserver.org/21108.html http://tc.eserver.org/21108.html 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. http://tc.eserver.org/20747.html http://tc.eserver.org/20747.html The single source in a robust single source system is not any one of the outputs that may be created from that source. The single source is an information set from which many outputs may be created. Designing an information set is different from designing a document. Greater structure is required, and that structure must be available to the process that creates information products as output, not simply to the reader. A good information set design involves creating a data model, mapping information relationships, and defining patterns of change. http://tc.eserver.org/20488.html http://tc.eserver.org/20488.html Okay, we've all fiddled with NavBars. In fact, MM's built-in Navigation Bar Builder is pretty sweet for creating NavBars with onMouseOver and onMouseOut behaviors giving your site that professional look. But what if your site changes frequently? One option is to bag the images and stick with a database-driven NavBar that uses a repeat region. We'll look at that approach first. Then we will see how we can replace UltraDev's hardcoded NavBar image behaviors with database-driven links and images. http://tc.eserver.org/20294.html http://tc.eserver.org/20294.html Many in-house information development groups are redefining their role (or seeking to justify their existence) around the concept of 'value-adding work.' But which tasks are value-adding? Finding an answer to this question is critical for the survival of information development groups. Unfortunately, there is no easy, 'one size fits all' answer, because the response depends largely on your point of view. Thus, deciding what is and isn't value-adding may require technical communicators to do more project-by-project task, audience, and media analysis than ever before. http://tc.eserver.org/20235.html http://tc.eserver.org/20235.html Content management systems are only as good as the content they manage. Garrity explores the care and feeding of low-budget clients who need high-quality content. http://tc.eserver.org/19813.html http://tc.eserver.org/19813.html Cautions that failing to focus on the people in the organization may diminish the success of a single-sourcing initiative. Covers changes that need to occur in the organization to support a single-sourcing initiative and ways to address issues of change. http://tc.eserver.org/19788.html http://tc.eserver.org/19788.html Tandem Computers Incorporated developed a new electronic information delivery system and changed internal publishing processes to achieve greater eficiency and customer satisfaction. We were able to move over 1,000 manuals and 11,000 pieces of support documentation along with education material from two different CD-ROM delivery products to one corporate viewer that supports publishing on both CD-ROM and the World Wide Web. The project included creating a new viewer using industry-standard components, creating new publishing tools, and establishing new corporate relationships and processes. http://tc.eserver.org/19641.html http://tc.eserver.org/19641.html In recent years, countless articles and conference workshops have touted single sourcing as the Holy Grail of technical writing. Countless articles and conference workshops have also told us that XML is our means to achieving the Grail. However, in the absence of any off-the-shelf products that facilitate XML and single sourcing in our current work environments, I suspect that most people, particularly in smaller companies, believe that implementing XML is too technically daunting, too expensive, or both. http://tc.eserver.org/19495.html http://tc.eserver.org/19495.html Reusable information objects and reusable learning objects are the building blocks of e-learning courseware and e-documentation. A strong business case can be made for implementing a single-source content repository for RIOs/RLOs to achieve reusability between enterprise applications. Keys to achieving reusability include: an effective metatagging scheme, appropriate levels of granularity, and adherence to standards such as the SCORM. http://tc.eserver.org/19373.html http://tc.eserver.org/19373.html Until recently, technical communicators created static content--content that is created in a specific way for a specific purpose (e.g., user guides and help) and that remains the same until the technical communicator deliberately changes it. As single sourcing has made it possible to write information once and use it many times, technical communicators have begun to create static customized content, which is designed to meet the specific needs of the user, the materials to be developed (such as user guides, reference guides, and training), and the delivery media (paper or online). The content is customized for a particular requirement at a particular time but cannot be changed without being regenerated by the author. Now, the ability to create dynamic content will change the way technical communicators envision, create, and distribute information. http://tc.eserver.org/19319.html http://tc.eserver.org/19319.html 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. http://tc.eserver.org/19155.html http://tc.eserver.org/19155.html Your organisation is unique, and as such, has a unique set of content management system (CMS) requirements. There is also no single 'perfect for everyone' content management system. Each product has its own set of strengths and weaknesses, and distinctive design principles. Unfortunately, the selection process followed by many organisations doesn't recognise this, leading to the purchase of a CMS which does not match business needs. Selecting a CMS does not have to be a lottery. By following a requirements-focused methodology, instead of a features-driven approach, the right CMS can be identified, and the business risks minimised. http://tc.eserver.org/19150.html http://tc.eserver.org/19150.html In March 2003, an online survey was conducted of consumer opinion about CMS vendor websites. This was extensively promoted through the CMS mailing lists, and on key CMS websites such as CMS Watch, the Intranet Focus and Step Two Designs sites. In total, 168 responses were made to this survey, representing consumers from across the globe, and in every type of organisation. This briefing provides a high-level summary of the results of the survey. http://tc.eserver.org/19153.html http://tc.eserver.org/19153.html At a basic level, implementing a content management system (CMS) is like deploying any other large software package. Fundamental project management principles must be followed, along with best practice technical guidelines. Beyond this, however, a CMS project presents a number of unique challenges. These must be recognised and addressed for the project to be successful. http://tc.eserver.org/19146.html http://tc.eserver.org/19146.html The rollout of a content management system (CMS) has the potential to impact on more users than any other system since e-mail. More crucially, the success of a CMS depends entirely on how much it is used, whether it is authors creating content, or users accessing the published site. It is these two challenges that place usability as a central issue to be raised and addressed. http://tc.eserver.org/19149.html http://tc.eserver.org/19149.html There are two fundamental aspects that must be satisfied if an intranet is to succeed: the intranet must meet staff needs; sufficient content and functionality must be created to meet these needs. These are the 'two faces' of the intranet, one looking towards staff and organisational needs, the other at the infrastructure and processes needed to meet it. http://tc.eserver.org/19032.html http://tc.eserver.org/19032.html 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. http://tc.eserver.org/19033.html http://tc.eserver.org/19033.html In most organizations, data is piling up by the minute: e-mails, names, addresses, transactions, you name it. As a result, finding what you need when you need it is becoming increasingly complicated, which is why more companies are deploying enterprise search tools. According to a recent report by Boston-based Yankee Group, 75 percent of businesses with more than 100 employees have some sort of enterprise search technology in place. The study also found that the bigger the organization, the more likely it is to invest in search technologies, as 91 percent of companies with more than $1 billion in annual revenue report having enterprise search capability. In 2001, a similar Yankee Group survey found that 63 percent of businesses employed search technology. In that year, enterprise search vendors generated $400 million in revenues. http://tc.eserver.org/19034.html http://tc.eserver.org/19034.html Digital asset management (DAM) software stores and organizes images, audio, video and other digital objects, making them easier to find, transform and reuse. And many companies are using DAM to provide a centralized way for employees and partners to locate and manipulate content-a big time-saver for all.