tekom 2016: Götterdämmerung?
After the anti-DITA insurrection at tekom 2015, the 2016 conference took a turn in a different direction.
Here are a few highlights. Keep in mind that the conference is huge; it would take a platoon of people to cover the 250 technical sessions.
Developing training websites in multiple languages
Tina Meißner of parson AG cowrote this case study.
This case study shows how Scriptorium Publishing created the free DITA learning website LearningDITA.com by combining the DITA learning and training specialization, GitHub, XSLT, video, and WordPress—and how parson AG adapted those technologies to develop the German site, LearningDITA.de.
Making localization “better”
This post is the first in a series about the value proposition of localization strategies. You can also see a presentation on this topic at LavaCon this October.
Localization issues are a primary reason companies seek help with a new content strategy. One of the most common questions we hear is, “How do we make our localization process better?”
When we’re asked this question, we turn the question around. What is wrong with your current localization process? What would you like to improve? How do you define “better?”
Glue strategy: connecting web CMS to CCMS
Web sites are fantastic at content delivery and generally terrible for content authoring. If you’re old enough (like me), you may have experienced the pain of hand-coding HTML or even editing HTML files live on your web server.
Pokémon GO and community documentation
Even if you aren’t twitchily checking your phone and resisting the urge to run outside to catch a Pikachu or Gyrados, you’ve probably heard all about the phenomenon of Pokémon GO. One of the most common criticisms of the game is that the in-app documentation is sparse at best. In response, the community banded together and began to document their theories and findings. You can readily find articles covering “eeveelutions,” theories on how to more easily capture Pokémon, and how to capture opposing gyms. It hearkens back to a time of meeting up in schoolyards to swap tips and rumors.
Reduce translation costs with XML
$0.21 per word.
That’s the average cost in the US to translate content into another language according to Slator, a translation news and analytics site. That number is not speculative; they analyzed the costs per word from over 80 actual proposals gathered by the US General Services Administration (GSA). You can view the source proposals here.