![]() |
![]() |
|
![]() |
![]() |
|
|
Categories
Powered by
|
TechCom The lady and the antelope: Suzanne Briet's contribution to the French Documentation MovementRemarkable woman in the Paul Otlet trajectory. "During her thirty years at the Bibliothèque Nationale (BN), Suzanne Briet (1894-1989) made important theoretical, organizational, and institutional contributions to the documentation movement in France. This paper attempts to place her documentation work within the context of the far-reaching reform of French libraries, with special attention to the transformation of the BN. Like her colleagues in special libraries, Briet embraced modernity and science. However, because of her strong orientation toward humanistic scholarship, she viewed documentation service and bibliographic orientation as an enhancement rather than a rejection of the scholarly traditions of the national library. This paper will focus on her efforts to integrate the innovative ideas of the documentation movement into the practice of librarianship at the Bibliothèque Nationale." Posted on April 02, 2013 | Permalink How the web designs informationGreat insight into paper versus digital, online, Web, 'what-have-you'. Now filter design included. "On paper, information design is monolithic and paternalistic. It is all about static structures page layouts, indexes, tables of contents all specified by a supervising author. On the Web, information design is distributed and democratic. It is all about filters, about designing filters that work for you, and about designing content to work with the filters. (...) Content needs to be designed for the Web. The filters need to be designed for the content." (Mark Baker ~ Every Page Is One) Posted on March 06, 2013 | Permalink The evolution of technical communicationInformation management and technical communication appear to be the parents of content strategy. "Over the years technical communication has transitioned from a conventional author-reader engagement to a realm of social collaboration. Let's take a look at how technical communication has progressed over time and the significant milestones along the way." (Monalisa Sen and Debarshi Gupta Biswas ~ tcworld) Posted on January 09, 2013 | Permalink Confab 2012: Thoughts and ReactionsFinally, somebody said it. "I was one of about 5 technical writers among the 650 attendees, which is why I found it surprising to hear Kristina Halverson say, We can learn a lot from tech comm. Let me repeat that. We can learn a lot from tech comm." (Tom Johnson ~ I'd Rather Be Writing) Posted on May 21, 2012 | Permalink Content Modelling: A Master SkillData, information, or content modelling: entities, properties and relations. Stuff and structure. "A content model is a powerful tool for fostering communication and aligning efforts between UX design, editorial, and technical resources on a project. By clearly defining the assembly model, the content types, and the content attributes, we can help make sure that the envisioned content strategy becomes a reality for the content creators. In my recent projects, I find that content modeling is more and more in demand. It's a valuable skill for any content strategist, especially those that strive for mastery." (Rachel Lovinger a.k.a. @rlovinger ~ A List Apart) Posted on April 24, 2012 | Permalink Content strategy in technical communicationAlso, content strategy can learn a whole lot from the field of Techical Communication. "In this webcast recording, Sarah O'Keefe explores how to develop a content strategy specifically for technical content. That means stepping back from the temptation to focus on tools and instead taking a hard look at what the users need and how best to deliver it." Posted on January 23, 2012 | Permalink The Strategic IAA column is like a site. Great to start but a hell of a job (for most) to maintain it on a regular basis. As always, benefit of the doubt. "This column explores the strategic aspects of information architecture and the tools to equip information architects for success. Topics will address the business, strategy, user experience, and implementation of strategic information architecture, including organizational, content management, and tactical considerations." (Andrea Ames and Alyson Riley ~ STC Intercom) Posted on October 05, 2011 | Permalink STC: Content Strategy SIG"The Content Strategy SIG is to be the STC home for members who are practitioners in this new space. The SIG is the forum in which to establish and develop the practice area of content strategy, particularly as it pertains to technical communication, to provide resources that prepare STC members wanting to transition to this as a career option, and to allow SIG members to support one another as practitioners as the field develops. Additionally, artifacts may be developed that allows practitioners to build a body of knowledge specifically pertaining to content strategy. The Content Strategy SIG was inaugurated in September 2009. As a new SIG, we are actively seeking members." (Society for Technical Communication) ~ dead-on-arrival Posted on February 23, 2011 | Permalink From DITA to VITA: Tracing Origins and Projecting the Future"DITA would have you believe that you can single source your way into every possible deliverable. In reality, you're just making potatoes in a few different ways (scalloped, mashed, boiled). You're still giving the user potatoes. VITA is a multimodal approach, giving the user a full array of nutrition options, so to speak. It educates and informs by touching almost every sensory input." (Tom Johnson) Posted on February 02, 2011 | Permalink Content Strategy: A Roadmap for Technical Communicators"(...) content strategy is more than a buzzword and goes above and beyond traditional project management or information architecture. Content strategy is a coordinated plan between the disciplines, which shows where an organization intends to put its content development efforts." (Peg Mulligan) Posted on January 24, 2011 | Permalink Findability and The Information Paradox"(...) a summary of why findability becomes an issue for technical writers, and what the information paradox is that we encounter. Then, in an usual ethical twist, I’ll explain why findability might not actually be an issue." (Tom Johnson) Posted on January 13, 2011 | Permalink Good Help is Hard to Find"One of the most fundamental rules of user experience on the web is that developers are rarely qualified to evaluate it. As developers, we know far too much about the web in general, and intuitively grasp details that mystify people who spend their days contributing to society in other ways. For this reason, it’s all too easy for us to build websites and applications that are hard to use. Good user testing during the development process can mitigate the problem, but in many projects, the testing budget is limited if present at all." (Lyle Mullican ~ A List Apart) Posted on August 18, 2010 | Permalink Why Help Authoring Tools Will Fade"Using any of the standard authoring tools — Flare, RoboHelp, Author-It, Doc-to-Help — leaves you with the ridiculous model of a single author working from a single vantage point from a single organization trying to pull together an ocean of information." (Tom johnson) Posted on November 25, 2009 | Permalink Technical Documentation Know-how"Know-how, checklists, tools and links, which will help you to create user-friendly software documentation such as manuals, online help, software demos and other forms of software user assistance." (Indoition Software User Assistance) Posted on October 28, 2009 | Permalink STC Content Strategy SIG"This site is the home of the Content Strategy SIG (Special Interest Group) of the Society for Technical Communication. (...) Content strategy is an emerging field of practice dealing with the planning aspects of managing content throughout its lifecycle. Strategy includes alignment to business goals, analysis, and modeling, and influences the development, production, presentation, evaluation, measurement, and sunsetting of content, including governance." (About Content Strategy SIG) Posted on September 09, 2009 | Permalink Architecting User Assistance Topics for Reuse: Case Examples in DITA"Single sourcing and its pragmatic flip side, reuse, remind me a bit of the early days of the personal computer. Everybody wanted one, but many weren’t sure what they would do with a computer if they got one. Even among seasoned user assistance architects, single sourcing and reuse remain elusive concepts. I recently heard someone at an STC chapter meeting define single sourcing as producing the same document as both a Help file and as a PDF file. Basically true, but one would hope there is more to it than that." - (Mike Hughes - UXmatters) Posted on May 26, 2009 | Permalink First 2 Words: A Signal for the Scanning Eye"Testing how well people understand a link's first 11 characters shows whether sites write for users, who typically scan rather than read lists of items." - (Jakob Nielsen - Alertbox) Posted on April 06, 2009 | Permalink Scatter/Gather"(...) a blog about the intersection of content strategy, pop culture and human behavior. Contributors are all practicing Content Strategists at the offices of Razorfish, an international digital design agency." - (About Content Strategy) Posted on April 02, 2009 | Permalink Hockey Sticks and User Assistance: Writing in Times of Resource Constraints"Many technical communication departments are experiencing flat budgets, meaning they’re getting only small or no increases in headcounts, capital expenses, or training dollars. Worse yet, many departments are facing reductions in these resources. These reductions cause production pressures that are often confounded by increases in development headcount, here or offshore. Since more code equates to more features, which in turn drive greater revenues, companies are more willing to increase development budgets. On the other hand, adding writers increases costs, which in turn reduces margins." (Mike Hughes - UXmatters) Posted on January 23, 2008 | Permalink WritersUA Conference Supplemental Materials Archive"Conference speakers, Peer Showcase presenters, and Exhibitors are invited to provide additional materials to supplement the detailed information included in the printed Proceedings. Additional items may be added to this page as they become available. (...) The Conference speakers retain all rights to their presentation materials. WritersUA only assumes the right to distribute the comprehensive, printed Proceedings. If you would like copies of presentation slides and they are not listed here, we encourage you to request them from the individual speakers. Most speakers have provided their email address in the printed Proceedings." (WritersUA) Posted on January 10, 2008 | Permalink Procedures: The Sacred Cow Blocking the Road"If this column's title sounds familiar to you, the bad news is you're getting old, but the good news is your memory hasn't gone yet. It was the title of a presentation I gave at the STC conference in Anaheim ten years ago. However, many of the points I made in that talk are still relevant to user assistance today, so I would like to update some of them and offer some new thoughts as well." (Mike Hughes - UXmatters) Posted on November 21, 2007 | Permalink Instructional Text in the User Interface: Some Counterintuitive Implications of User Behaviors"User assistance occurs within an action context—the user doing something with an application - and should appear in close proximity to the focus of that action - that is, the application it supports. The optimal placement of user assistance, space permitting, is in the user interface itself. We typically call that kind of user assistance instructional text." (Mike Hughes - UXmatters) Posted on March 09, 2007 | Permalink Jon Bosak Closing Kenote XML 2006"It's hard to remember now just how different this community was ten years ago. There were only a few hundred SGML experts in the world, a goodly number of whom came to this conference every year. Very few groups in existence today could boast the level of intelligence, the breadth of interest, and the depth of independence, not to say downright weirdness, evidenced by the SGML community of a decade past." (XML 2006 Proceedings) - courtesy of timoreilly Posted on January 13, 2007 | Permalink User Assistance in the Role of Domain Expert"This article explores the role of user assistance in providing domain-centric online Help - rather than Help that simply explains obvious user interactions with well-designed user interfaces - and provides a pattern for and examples of expert guidance." (Mike Hughes - UXmatters) Posted on January 10, 2007 | Permalink New Life for Product Documentation"We usually assume that documentation is used after a product has been purchased, as part of the process of learning or setting it up. But these are all examples documentation as part of the purchasing-decision process, looking for information beyond the lists of features or simple technical specifications on data sheets." (Whitney Quesenbery - UXmatters) Posted on August 20, 2006 | Permalink 10 DITA Lessons Learned From Tech Writers in the Trenches"This exclusive and informative top ten list is based on interviews with technical writers at more than 20 software companies - tech writers that are actually using DITA to create documentation today. It's jam-packed with useful advice, practical tips, honest warnings, and lessons learned." (The Content Wrangler) Posted on August 10, 2006 | Permalink Minimalism: The Minimalist Model applied to documentation and training"The Minimalist theory of J.M. Carroll is a framework for the design of instruction, especially training materials for computer users. The theory suggests that (1) all learning tasks should be meaningful and self-contained activities, (2) learners should be given realistic projects as quickly as possible, (3) instruction should permit self-directed reasoning and improvising by increasing the number of active learning activities, (4) training materials and activities should provide for error recognition and recovery and, (5) there should be a close linkage between the training and actual system." (Martin Ryder) Posted on June 18, 2006 | Permalink Apple Style Guide: 2006 version
|
|