General User Discussions
i'm trying to convince our developers and intermediate management to focus on DITA in our next software generation, a web-based application for government administration. the difficulty is: i'm left alone on that task and have no help whatsoever since documentation is seen as very unimportant (but everybody will be complaining in the end when there's no documentation).
Adobe(r) Systems have announced that they will be giving away full copies of Adobe Technical Communication Suite (worth £1320 each) at X-Pubs 2008! Chances to win one of them are 1 in 15.
TCS features the full DITA application for FrameMaker, allowing you to create and publish DITA documents to multiple formats, as well as pass them on to Adobe Acrobat(r) to enrich your PDFs with 3D and rich media like Adobe Captivate(r) simulations.
What is a good short description for a task?
Some of the short descriptions indicated as "good" in the class assignments simply restated information that was in the short description of the related concept. The task's short description may have been written differently and in the imperative, but it was redundant information.
- Review the presentation at http://www.ditausers.org/tutorials/basics/Priestley_Authoring/
- Read section 3.1 of the DITA 1.1 architectural specification:
- Read the description of <shortdesc> in the DITA 1.1 language specification: