DITA : s’informer et se former

DITA, … vous hésitez ? vous voulez vous informer ?

Excellente démarche ! Il est toujours bon de s’informer avant de trancher.

Logo DITA
L'oiseau qui fait aimer DITA...

 

 

Vous pouvez commencer à naviguer et picorer les informations pertinentes à partir des sites disponibles sous tout format :
DITA – Introduction par Bernard Aschwanden

DITA : pourquoi faire ?__________________________________

(1) Business benefits of DITA, par Laura Bellamy
Laura Bellamy est egalement co-auteur de l’excellent manuel « DITA Best Practices »

(2) DITA adoption – SWOT Analysis

Quels sont les critères à prendre en compte avant de prendre sa décision ? SWOT : strength, weakness, opportunity, threat

(3) The business case for DITA

DITA : comment ca marche ?

(4) Why DITA?
The industry goal is to encourage the development of interoperable tools.
The organization goal is to make documentation easier to produce.
The end-user goal is to make documentation easier to use as well as more valuable for the user.

(5) XML and DITA adoption rates.

Qui a pris le virage DITA ?

 

DITA : les expériences__________________________________
(1) Twelve DITA Implementations. The lessons learned – DCL LEARNING SERIES

(2) 10 DITA lessons learned from tech writers in the trenches

A méditer : One Writer’s Legacy Content Conversion Process Timeline
It took me 100 hours to convert 400 pages of unstructured FrameMaker content into DITA. The approach I took was to:

1. Clean up the styles in the source FrameMaker files (16 hours)
2. Create a mapping table that mapped these styles to DITA elements (8 hours)
3. Use the mapping table to get from unstructured to structured FrameMaker (1 hour)
4. Save the structured FrameMaker files as XML (1 hour)
5. Clean up the XML files to make them parse (24 hours)
6. Perform manually what didn’t come across in the conversion—see below (46 hours)
7. Create ditamaps for each book (4 hours)

I had to do the following tasks manually:

* Apply hierarchy to nested topics and lists
* Re-apply cross references
* Cut-and-paste table cell text
* Add graphics

Using this writer’s legacy content conversion metrics as a baseline:

* Converting 400 pages of content would take 100 hours (or 2.5 weeks)
* Converting 4,000 pages of content would take 1000 hours (or 25 weeks)
* Converting 40,000 pages of content would take 10,000 hours (or 250 weeks)

   

Clair et structuré

 

 

Attention à ne pas vous compliquer la vie – Evitez la SPECIALISATION trop souvent superflue
Resist temptation to specialize

 

 

 

DITA : La technique______________________________________

(1) DITA authoring – Basics – excellent – M. Priesley
Creating task-based navigation with DITA  (excellentissime).

(2)  dita 1.2 – part 2  – New conref and subject scheme

(3) DITA Best practices, Tony Self – Webinar

(4) DITA Metadata

(5) What’s new in DITA 1.2 – Part 1 – Keys and Conkeys – (par Noz Urbina)

 

DITA : les avantages – La ré-utilisation de contenu____________
(1) Developing a DITA-based content strategy for Reuse – DCL (Ann Rockley)
Presentation about Re-use  « Conquering the Mountain of Legacy Data »

Souvenez-vous, c’est essentiel : « It’s not about the code, it’s about the strategy »  (Ann Rockley, Webinar, DC Laboratory, 28.09.2011)

(2) Passage à DITA :
Are you ready for conversion?  JoAnn Hackos – DCL Webinar series

 

Reducing cost_____________________________________
(1) Using DITA to reduce cost while increasing content quality

 

Quels coûts ?

(2) DITA ROI – Mark Lewis, Quark Inc – Translation costs, Content re-use

 

(3) Metrics, ROI, and Other Stories from a Mature DITA CMS installation
Keith Schengili-Roberts, Conference Congility London 2011

– Excellente démonstration du calcul de retour sur investissement après implémentation d’un système de gestion de contenu et d’une rédaction sous DITA.

 

 

Pour suivre l’actualité du développement DITA, il suffit de se brancher sur :
www.ditaworld.com
www.ditanews.com/resources/
dita.xml.org

Laisser un commentaire