For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

Search results

Recording and slides from "Jekyll vs. DITA: Bridging the Gap Between Tech Comm and the Web" presentation

Series: Jekyll versus DITA

by Tom Johnson on May 14, 2015
categories: dita • jekyll • podcasts

Yesterday I gave a presentation to STC Berkeley about ways to bridge the gap between tech comm tools and web development tools. After talking about innovation patterns, I focused on static site generators, specifically Jekyll. I also explained how DITA compares to Jekyll.

Slides

Here are the slides:

Jekyll vs DITA presentation

Audio recording

Here's the MP3 audio file:

Listen here:

(Sorry, my attempts to record the screen using Camtasia failed -- Camtasia crashed. I think my MacBook Pro Retina display didn't jive with the old projector I was hooked into.)

Links to more information

Note that this presentation is similar to the keynote I gave at tcworld India. Personally, I felt the India presentation went better. If I were giving this presentation again, I would probably drop the DITA comparison, shorten the exploration of innovation, and just show static site generators in depth.

Also see the Jekyll Versus DITA series for more detail about the tool comparisons.

Sponsored

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.

If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.

Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.