Although this course has focused heavily on tools, I want to emphasize that content always trumps tooling. The content should be your primary focus, not the tools you use to publish the content.
Once you get the tooling infrastructure in place, it should mostly take a back seat to the daily tasks of content development.
I’ve changed my doc platforms numerous times, and rarely does anyone seem to care or notice. As long as it “looks decent,” most project managers and users will focus on the content much more than the design. In some ways, the design should be invisible and unobtrusive, not foregrounding the focus on the content. In other words, the user shouldn’t be distracted by the tooling.
For the most part, users and reviewers won’t even notice all the effort behind the tools. Even when you’ve managed to single source content, loop through a custom collection, incorporate language switchers to jump from platform to platform – the feedback you’ll get is, “This sentence is incorrect.” Or, “There’s a typo here.”
At this point, think about your requirements, your audience, and try to pick the right tools for your situation. Here are a few questions to consider as you think about the right tool for you:
If you would like to contribute back and encourage more available content and resources, you can click the Donate button below and contribute any amount.
Get new posts delivered straight to your inbox.
© 2017, Tom Johnson