references - look for titles with command names in lower case.topic types - many not need immediately, but much easier to add at conversion time, not after.topics - break out based on heading levels.if active docs, do pre-conversion cleanup.if you don’t need the docs immediately, convert after.either use everywhere or nowhere - not a mix everywhere is best, but time consuming.improve conversion by adding paragraph breaks between and or.doing and undoing something = two tasks.if there are two ways to do something, you need two tasks.do not include multiple types on content in the one topic - just one.4 basic topics - task, concept, reference, and troubleshooting.topic-based - smallest unit of content that makes sense by itself.minimise inline x-refs - move into a relationship table.rewrite for localisation/translation even if not going there yet - consistent terminology, concise, clear (avoid idioms), grammatically complete (don’t forget ‘that’).ensure users can find the info they need.recognise the importance of troubleshooting info.setting up storage, reuse and publication facilities.I tried to keep up with her but these notes may be missing a few points. She talked about pre- and post-conversion tasks for DITA, amongst other things. This was an info-filled talk by Helen St Denis, Conversion Services Manager, from Stilo. ‘Tis an unweeded garden that grows to seed - cultivating a weed-free content ecosystem people and processes are the hard part - tools are the easy part!.Publishing options - DITA-OT XML Mind DITA Converter Adobe AEM Publishing.Tools that support LWDITA include oXygen XML Editor, Author, Web Author SimplyXML Content Mapper and others.LWDITA - start simple, eventually more tool support, don t need XML.Full DITA - advanced features, more flexibility, mature tools.LWDITA is less flexible but easier to learn.LWDITA - has only 2 doc types (topic and map), 40 elements types (33 from DITA 1.3, 7 for multimedia support), and 3 formats (XML, HTML5, Markdown).Simplify the model - no longer reliant on XML schema cross-format content standard.Why isn’t DITA everywhere? perceived complexity (too many tags, too hard to customise, steep learning curve) and it’s XML (software developers mostly use XML for data, so when JSON came along, XML was dead for them bias against XML in favour of Markdown, HTML5, custom formats).DITA is a standard, which means it’s portable and scalable.how and what to measure - process efficiencies to reduce costs revenue growthĬross-format and cross-silo: Lightweight DITA (LWDITA) for intelligent content.reuse components across business verticals.think about components, not complete docs.search is a headache, find is a solution (think of searching for your car keys versus finding your keys ). ![]() content is cross-department and cross-functional - it shouldn’t live in silos.Docs can reduce costs AND generate revenue track/share costs - you can cut costs by sharing content, but even better is to generate revenue. ![]() I’ll have to watch the recording and view the slides later. Diversify your content ecosystemīernard Aschwanden took us through a heap of information, a tiny amount of which I captured in notes. Here are my notes from the sessions I attended. The last day of LavaCon 2018 was full of breakout sessions, with no plenary sessions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |