My colleagues and I were talking the other day about where we're going to publish some help content. The scenario we're addressing is a project that will be translated into 38 separate languages. Additionally, there are 28 roles for the system. This means there would potentially be 1,064 outputs (38 x 28), assuming help is to be specific to each user's language and role. This is a tremendous amount of material to generate and keep track of, and the thought of it overwhelms me.
We're implementing Author-it in my organization, and one of the technical leads showed us Author-it Aspect. Apparently this tool would allow us to publish all the content in the same output. Then through the user's profile, he or she would see the help material that is relevant to his or her role and language. Rather than 1064 outputs, we'd have just one.
Here's the demo that my colleague showed us. It's a recorded webinar that I'm reposting here with Author-it's permission.
You'll see that you can select options to see different views into the content. My understanding is that through an Author-it Aspect API, you can configure the views to your user's profile (assuming the user logs in). Otherwise, if not logged in, the user would select the view from the Options menu. But here's the point: it's all the same help file. There aren't hundreds of different help outputs to coordinate behind the scenes.
This seems like much needed technology that would simplify a lot of robust publishing situations. Granted, I think Aspect requires its own server and is somewhat costly, but the time it would save in managing the content might be worth it. Is anyone out there using Author-it Aspect? I'd love to hear about your experience.
For more information, see Author-it Aspect.
8/26 update: I recently learned that Aspect doesn't support multiple languages as variants. This functionality won't be available until version 6.0 of Author-it is released (within a few months).
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include technical writing, authoring and publishing tools, API documentation, tech comm trends, visual communication, technical writing career advice, information architecture and findability, developer documentation, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here.