Scenari Dokiel

For who? Dokiel is intended for technical writers and trainers of software editors, manufacturers, IT management teams, support services...

For what? Dokiel enables to create documentations and training medium. Documentations: User guides (web and PDF), Tutorials, Installation and operating guides, Functional and technical specifications, Multi-entries reference website Training medium: Slideshow and video-projected training, Trainee booklet (PDF), Medium for the trainer, E-learning modules, Self-assessment...

How does it work? Dokiel encourages to structure the editorial content using fragments:

• Concept: to define the notions linked to the business area or the specific terms of a tool or software,
• Operating process: to describe step by step the actions of a procedure, enriched with videos or screenshots,
• Screen: to enrich a screenshot or a picture with area by area explanations (interactive screen on web medium),
• Synoptic tree: to create a mind map, by organizing nodes in a tree-like form. These fragments of contents can be referenced in one or several documents (User guides, Reference documentations or Training modules) in order to generate the document in the appropriate format for the desired distribution channel (PDF, web, SCORM...).

What interests?

• Use a writing guide making easier the structuring and writing of the content.
• Design advanced business objects (synoptic tree, interactive screen, procedure reader, quiz...) without technical prerequisite, nor HTML knowledge.
• Automate the multi-format (pdf, web, scorm) and multi-channel (internet, intranet, training platform, printing,...) publication, from a unique source of content.
• Preserve the visual identity of the organization with skins (layout graphic design) defined and applied automatically for each type of document.
• Rearrange fragments of content to create various versions of the documentation, without duplication of the content.
• Reduce the update time: the modification of a fragment of content is reverberated on all the documents that use it.
• Share fragments of content between the documentations and the training medium to make the information update more reliable.
• Adapt one documentation for various products, by using advanced editorial mechanisms, such as variables or conditions.
• Create a reference documentation with several entry points (search engine, index of the procedures, glossary, themes tree) and offer a customization of the content depending on the user profile (profiling).
• Make and follow the translation of a documentation.
• Organize the teamwork: writing, review, validation (in a client/server environment).
• Use XML standards to store and exchange your contents (with translators, printers,...).