---
title: "Chapter 11: Publishing tools and workflows"
date: 2026-10-03
description: "Download PDF Publishing technical documentation typically involves following docs-as-code tools and workflows. For open source projects, GitHub is frequently used to manage content. But even within..."
canonical_url: https://idratherbewriting.com/learnapidoc/publishingtools
---

> 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.

# Chapter 11: Publishing tools and workflows

[Download PDF](https://www.buymeacoffee.com/learnapidoc/e/146076)

Publishing technical documentation typically involves following docs-as-code tools and workflows. For open source projects, GitHub is frequently used to manage content. But even within the enterprise, Git is still common. A typical documentation workflow involves making pull requests with doc changes that get rolled into the main branch. In this chapter, you explore some of these workflows using tools like GitHub wikis, Jekyll, CloudCannon, Oxygen XML and more. It’s important to become comfortable working from the command line to create branches, get updates, perform merges, and push builds.

- [Activity: Manage content in a GitHub wiki](https://idratherbewriting.com/learnapidoc/pubapis_github_wikis.html)
- [Activity: Use the GitHub Desktop Client](https://idratherbewriting.com/learnapidoc/pubapis_github_desktop_client.html)
- [Activity: Pull request workflows through GitHub](https://idratherbewriting.com/learnapidoc/pubapis_github_pull_requests.html)
- [Jekyll and CloudCannon continuous deployment tutorial](https://idratherbewriting.com/learnapidoc/pubapis_jekyll.html)
- [Using Oxygen XML with docs-as-code workflows](https://idratherbewriting.com/learnapidoc/pubapis_oxygenxml.html)
- [Case study: Switching tools to docs-as-code](https://idratherbewriting.com/learnapidoc/pubapis_switching_to_docs_as_code.html)
- [Tools FAQ](https://idratherbewriting.com/learnapidoc/docapis_faq_tools.html)