My API workshop will more or less follow the same content as my API doc course. This content is online and available right now.
For my presentation on Jekyll, here’s the presentation title and description:
Writing tech docs like a hacker with Jekyll
Static site generators are a new breed of documentation tools that are much more common in engineering groups where developers contribute to the documentation.
Jekyll is one of the most popular static site generators, but it is highly similar to others in the same category such as Docpad, Middleman, Wintersmith, and Octopress. You can see a more comprehensive list of the top static site generators at Staticgen.com.
Jekyll projects approach doc as code. All the files are open and editable within a code editor, and your files can live in the same repository as your program code or within the same version control workflow.
Although developers and web engineers love Jekyll, there are significant challenges to overcome when adopting Jekyll for any robust tech comm publishing scenario. Some of these challenges include conditional filtering, single sourcing, PDF output, a robust TOC, search, context-sensitive help, collaboration, SME review, and more.
In this presentation, I’ll share my adventures in using Jekyll and how I dealt with each of these challenges.
The 2016 STC Summit will be held in Anaheim, California on May 15-18.
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.