#26972
ניהול תוכן (content management או בקצרה CM) הוא סט של תהליכים וטכנולוגיות, בהם משתמשים כדי לקיים מחזור החיים של מידע דיגיטלי. דוגמאות קלאסיות למערכות ניהול תוכן הם מערכת ויקיפדיה, מערכות לניהול תכנים של אתרי אינטרנט, ומערכות טיפול בידיעות עיתונאיות.
Wikipedia (2006). (Hebrew) Articles>Content Management
#31840
A Team Approach to Information Architecture
A case study of a team approach to information architecture at Duke University by graduates of the Duke Continuing Studies Technical Communication Certificate program.
Olson, Amy, Sangita Koli and Dino Ruggiero. Carolina Communique (2008). Articles>Business Communication>Information Design>Content Management
#28198
Advertisers are Missing the Internet Connection, OPA Report Reveals
According to a June 2006 study conducted on behalf of the Online Publishers Association (OPA) by the Center for Media Design at Ball State University, advertising dollars aren't keeping up with skyrocketing consumer web demand.
Dye, Jessica. EContent (2006). Articles>Content Management>Marketing
#18322
I have seen the future and it works. We have just finished our first single-sourcing project using mif2go to convert FrameMaker source files to HTML Help *.chm files. These files are also the source of our printed user guide AND a hyperlinked PDF of the user guide placed on the distribution CD. There was considerable once-off pain setting up conversion templates (including CSS files) and conversion options but our next project will be much faster. The converted files DO NOT require ANY hand tweaking -- we just hand over to the release people to put the *.chm file on the installer CD. Our testing and support people are rapt, and consider the new help far better than the old help. An outsider would have no inkling that the help was produced in this way.
Finger, Hedley. InFrame (2002). Articles>Content Management>Single Sourcing
#27997
After the CMS Implementation Project
Much effort is focused, on the selection and subsequent implementation of a content management system (CMS). While it is obviously vital to ensure that the initial implementation project is successful, this is only the beginning of an ongoing commitment to growing and enhancing the use of content management throughout the organisation.
Robertson, James. CM Briefing (2004). Articles>Content Management>Project Management>Workflow
#27044
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.
Downes, Jonathan and Joe Walker. CMSwatch (2006). Articles>Content Management>Web Design>Ajax
#25378
An Overview of Single Sourcing with an XML Content Management System
Creating an XML-based Content Management System to single-source technical publications is as simple as 1 - 2 - 3. OK, maybe it isn't quite that easy, but this article discusses how it can be done.
Sapir, Rick. KeyContent.org (2004). Articles>Content Management>Documentation>XML
#18432
An information architecture analysis of top business analysts' web sites.
Fox, Chiara and Keith Instone. Argus Center (2001). Articles>Content Management
#28782
Ann Rockley on the Rockley Group Blog and a New CMS Report
Ann Rockley shares information about an upcoming report on component content management systems her group will be releasing this summer. She also says the Rockley Group is launching a blog to provide quicker information to users in a more interactive way. She talks about the growing presence companies have in the blogosphere, and why they chose WordPress as their blogging tool.
Rockley, Ann and Tom H. Johnson. Tech Writer Voices (2007). Articles>Interviews>Content Management>Podcasts
#27002
Applying "Mass Customisation" Manufacturing Principles to Solve Technical Communication Problems
This article discusses how organisations can resolve the conflict between the need to produce bespoke, customer-specific, technical communication and the need to re-use as much information as possible. It begins with a description of the conflict and resulting trade-off and then compares it to the field of manufacturing, which has found ways to deal with a similar issue. Universal information modules are introduced as the solution - these allow the manufacturing principle of mass customization to be applied to technical communication. The article ends by outlining the requirements needed for supporting tools in order to adopt this solution.
Rombauts, Yves. Cherryleaf (2005). Articles>Content Management
#25979
Architectural Considerations in Digital Asset Management
What is the proper foundation for an enterprise-scale Digital Asset Management (DAM) system? How much of that system should be part of an organizations shared infrastructure and how much should be tailor-made to a specific application? There is no single answer to these questions, but changes in the technology industry are forcing everyonevendors and customers aliketo change their assumptions about how DAM systems will be built. This paper explains how the content-management infrastructure is changing, why that matters to DAM, and what benefits can be derived from leveraging a content infrastructure for DAM. Examples from an enterprise implementation at the University of Michigan illustrate the types of architectural issues and requirements that affect platform choices when selecting a digital asset management system.
Walter, Mark. Gilbane Report (2004). Articles>Content Management>Multimedia
#25104
Ask Tony: Future of Microsoft CMS 
Microsoft has in no way abandoned the web content management market.
Byrne, Tony. CMSwatch (2005). Articles>Content Management>Software
#30604
ATAG (Authoring Tool Accessibility Guidelines) Assessment of WordPress
This document assesses WordPress 2.01 against the Authoring Tool Accessibility Guidelines 1.0.
Clark, Joe. JoeClark.org (2006). Articles>Web Design>Accessibility>Content Management
#14245
Reviews briefly the systems that Gery presented in Electronic Performance Support Systems and then focuses on the 19 attributes she subsequently developed to elucidate them. Then examines the 1997–2001 competition award winners in light of these attributes. Doing so, it turns out, both clarifies the attributes and suggests a few new ones.
Marion, Craig. Technical Communication Online (2002). Articles>Content Management>Online
#25654
Author-Friendly Electronic Submission to SGML-based Academic Journal
I and my co-workers developed an author-friendly method for electronic submission to an academic journal, which is published using a SGML (Standard Generalized Markup Language)-based system. The method uses a style function and RTF (rich text format), and can be used in popular word processing software: Microsoft Word, WordPerfect, PageMaker, etc. The method has been adopted in Bulletin of Chemical Society of Japan (CSJ) since April 1994, which is the monthly English journal of CSJ, and has been published since 1937. The journal has been published in a SGML-based system since January 1993. Our electronic submission method will be included in SIST (Standards for Information of Science and Technology) No. 14 (draft): 'Guideline for electronic submission', which is considered in SIST Committee in Japan, and will be published in near future.
Ishizuka, Hidehiro. ISRDP in Digital Libraries (1997). Articles>Content Management>SGML
#29750
When it comes to information management or content management strategies, particularly at the enterprise level, there is a strong tendency (and desire) to create long-term plans. This briefing will explore some of the issues encountered when creating and executing long-term plans, and will argue for an approach that delivers benefits on a much more frequent basis.
Robertson, James. Step Two (2007). Articles>Content Management>Content Strategy
#14248
Back to Fund-amentals: The Business Realities of Funding for Performance Support Projects 
Although electronic performance support systems (EPSSs) sound like exciting projects to technical communicators and instructional designers, many proposed EPSSs stay on the drawing boards because the organizations for whom they were designed choose not to fund them. In general, EPSSs require more up-front investment than traditional documentation and training. That additional expense, sometimes increasing up-front expenses by several times, could be enough to stop a project unless the designers can explain how the organization can benefit from this additional investment. In fact, most often, these organizations decline to fund the proposed EPSSs because the financial benefits of the EPSSs are not explained, and so the proposed EPSS is perceived to exceed the cost of designing and developing it. In other words, the businesses do not perceive that the EPSS is a good investment of their money.
Driscoll, Margaret and Colin Hynes. Technical Communication Online (2002). Articles>Content Management>Proposals
#30145
Benchmarking the Document Management Process 
The Bank of Canada manages the public debt as fiscal agent, for the Federal Government. As a public service organization, it is committed to deliver quality services to its clients in a cost effective and efficient manner. Recognizing that a fundamental role of documentation is to provide continuity within a changing environment, the Public Debt Department (POD) piloted best practices benchmarking of its internal documentation unit with partners identified as having best-in-class processes.
Edwards, Roy, James D. McGuire and Shirley A. Hancock. STC Proceedings (1997). Articles>Content Management>Assessment>Case Studies
#28933
Better Content Management through Information Architecture
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.
Nasser, Masood. Boxes and Arrows (2007). Articles>Content Management>Information Design>Content Strategy
#29742
Blog 101: An Overview of Weblog Technologies
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.
Berry, Robert R. STC Proceedings (2004). Articles>Content Management>Information Design>Blogging
#27131
Blogs and One-Step CMSes are the Future of Web 2.0
Last year before I discovered Drupal and a host of other Content management systems I was building websites from scratch. I spent hours in PHP and Active Server Pages coding and designing. I was quite happy doing so. But then I came upon a flaw in the business plan of the company where I worked. It seemed we were doing the same thing over and over again only with slight differences in the end result. These differences were the reason I was busy all the time but could never catch up to the work load. What we needed was a finished product that allowed us to produce addons to satisfy the individual needs of each client.
Hiveminds (2006). Articles>Content Management>Software
#25481
Blogs and Technical Communication
Blogs are a simple, yet powerful tool and their popularity is rapidly growing. How are blogs affecting the community and technical communication?
Cottrell, Christina. Michigan State University (2003). Articles>Content Management>TC>Blogging
#25456
Content Management is starting to wrestle with what Clayton Christensen calls The Innovator's Dilemma: the inability of successful companies to adapt to a new, disruptive technology.
Hiler, John. Web Crimson (2002). Articles>Content Management>Technology>Blogging
#23944
Bridging the Back-Office/Front-Office Gap
With 75% of your organization's information contained in unstructured formats, can you transform it into 'usable content?' The problem that e-business exposes most often is inadequate integration.
Gross, Mitchell. KMworld (2001). Articles>Knowledge Management>Content Management
#28196
A triple-barreled question facing many enterprises today is whether to use an application-building tool or 'framework' to build a content management system (CMS); to buy one of the many out-of-the-box finished products in use by major Web sites; or to simply rent a CMS from an application service provider (ASP) and avoid the headache of running an application server in the enterprise's data center.
Doyle, Bob. EContent (2004). Articles>Content Management>Software
