Author: Sydney Jones

It is rare for documentation teams to not use some form of database or repository for storing their technical content. A documentation team of any size will generate significant amounts of content over time that eventually outgrows shared network folders...

As the DITA standard celebrates its 10th anniversary this year, we reflect on its existence over the last decade and note how much has changed in the way we think about structured technical documentation. DITA continues to evolve with the DITA 1.3 specification expected to...

Author Richard Forster Varian Medical Systems, Inc. It ain’t art. At the very latest, when moving from unstructured to structured authoring, the last lone ranger in the technical publications department will realize that technical writing is not an art, but a craft—an engineering craft. Artistic attitudes, flights of...

Author Leigh White DITA SPECIALIST AT IXIASOFTContent reuse is one of the main “selling points” of DITA. Teams looking to make the transition to DITA are excited by the possibility of reducing the amount of new content they have to create and leveraging their existing content in...

Author Leigh White DITA SPECIALIST AT IXIASOFT  DITA 1.3 introduces scoped keys, which represent a huge improvement over the key functionality introduced in DITA 1.2. In DITA 1.2, a key could have only one definition with a root map. DITA 1.3 allows a key to be redefined at...

AuthorKEITH SCHENGILI-ROBERTSSENIOR DITA CONTENT STRATEGIST MARKET RESEARCHER AT IXIASOFT CHAIR OFOASIS DITA ADOPTION COMMITTEEKeith Schengili-Roberts has more than 25 years of experience in the documentation industry as both a technical writer and documentation architect. Keith has recently joined IXIASOFT as a DITA Information Architect, representing the company...

X