My docs-as-code toolchainI use a set of open-source and well document tools to create and manage documentation at an organizational level.
* [Sphinx](https://www.sphinx-doc.org/) for complex documentation.
* [Pandoc](https://pandoc.org/) and [Jekyll](https://jekyllrb.com/) for simpler or one off documents.
* [MikTex](https://miktex.org/) to create [LaTex](https://www.latex-project.org/) PDFs from Sphinx or Pandoc.
**Documentation lifecycle tools:**
* [Git](https://git-scm.com/) as a version control system.
* [GitLab](https://gitlab.com/) or [GitHub](https://github.com/) as a GUI cloud based storage, collaboration, and workflow tool.
**Automatic distribution:** [GitLab](https://gitlab.com/) or [GitHub](https://github.com/) as a DevOps platform to enable automatic distribution of documentation via CI/CD.
**Data analysis and manipulation:**
* [Pandas](https://pandas.pydata.org/) for data manipulation.
* [Matplotlib](https://matplotlib.org/) to automate graphs from raw data.
* [Regex](https://en.wikipedia.org/wiki/Regular_expression) for grammatical analysis.
* [GIMP](https://www.gimp.org/) for image manipulation.
* [Inkscape](https://inkscape.org/) for creating vector images.
* HTML/CSS for website styling.
**Text editor:** [Atom](https://atom.io/)
We electronically control revisions for this topic and deploy it directly online. Any copies you generate from the latest revision are uncontrolled. Ensure you refer to the latest revision online when possible.