How I used Python to Collect Project Documentation

Documentation is always a challenge in the world of Software Engineering. Often times documentation is the last thing that gets done, and it’s hard to keep it updated. Some people make the argument that the code is the documentation, but you still need guides and other instructions for people to use your project.

One big challenge when you have a big project, is that even good documentation can be overwhelming. Often times people will create GitHub Wikis that are nothing more than several different markdown files linked together. This works, but makes it easy to get lost in the weeds. Moreover, it would be really helpful if there was a way to organize this documentation in a single place.

Recently, I wanted to gather a large number of markdown files from a project I was working on. Basically, I needed to organize documentation into a single place. This place had to be easily readable, can be shared, and can be searched.

So I found MkDocs.

MkDocs is a site generator that was written in python and is also open source. The site generator basically creates a static site using markdown files. You can host your site in GitHub Pages or an AWS S3 bucket static hosting. You can do everything using the MkDocs CLI, and just requires you to have python installed on whatever machine you’re using.

MkDocs also uses themes, so you can pick how you can customize what you want your site’s look and feel to be. For any MkDocs project I’d recommend the Material Theme which is built using Google’s Material Design Specification.

MkDocs creates the site using a yaml file to determine navigation, and a docs folder for the markdown files you want in your site. The yaml file is basically instructions for MkDocs to create the site and usually looks similar to this:

site_name: firstSite 

This example shows a site named “first site” that has two markdown files in the docs folder to include and The generated site would enable lefthand navigation from the main homepage and look like the following:

image copied from the MkDocs page here

Since MkDocs uses markdown files, this was perfect for what I was wanted to do. All I needed was to gather my projects README files in one place, and build in navigation where appropriate.

With my site generator picked out, I created a python script that walked through the project and collected the files. Then I used npm to create scripts that automated this process, so whenever I wanted to update the documentation site, I just ran npm run deploy and pushed updated documentation to the repo’s GitHub pages site. With this process, I now had all the documentation in one location that was easily searchable and can be shared.

In the following sections, I’m going to walkthrough how you can create a documentation generator similar to what I did.

I’ve created a sample project on GitHub that I’ll be using for my explanation. This sample project uses the Angular Material GitHub project as a source for gathering documentation. You can change this to be anything, I’m just using Angular Material here since it has a lot of README files and is a good example.

Using My Sample Project

First, go to GitHub and create a fork of my sample project. Then do a Git Clone of the fork you created.

You should now have a project that has the following structure:

├── generated-site
│ ├── base.yml
│ └── docs
│ └──
├── package.json
  • The generated-site folder has the main files and folders that MkDocs will use to generate the site. When our scripts run, this docs folder will also create a site-files folder to hold the markdown files that MkDocs will use.
  • The is sitting inside the docs folder for convenience, and to use as a home page for the generated site. You can just leave this file blank because it’s just as a landing page.
  • The base.yml file will be used by the python script to create a custom yaml file for MkDocs to use when creating the site. As the python script runs, it will write values to this file. The file I’ve created includes the material theme, but you can customize this for your project if you wanted to.
  • I used npm init to create the package.json at the project’s root. If you want to use this for your project, you’ll need to change the values for author, project, etc. to suit your needs. The npm scripts that I’ve included inside this file also allow us to build and deploy our project.
  • The file is the python script which I will cover in the next section.

Creating the Python Script

The python script in my sample project collects the markdown files from your GitHub project into a folder that MkDocs can read from. The script basically just walks through a local copy of your GitHub project, and then generates a staging area that MkDocs will use to create your documentation site. I’m going to walk through the script section by section, and show you were you can add customizations.

So let’s get started!

Here is the first part of the script:

This first part is pretty straightforward. We are declaring the global values, and then we define cleanup functions that our script will use before it runs.

If you notice the create_files_and_folders function here is actually creating several subdirectories. This caters to the Angular Material repo, but you can change this to be whatever you want for your project.

Here is the second part of the script:

This part is also pretty straightforward. The function select_md() walks the project directory to find the markdown files, and then the function copy_md() copies these files over to the site directory we created in the earlier section.

If you notice, the copy_md function is actually looking for files that have “/src/lib” and other specific values in them. The multiple loops look for these values, and when they see them they copy them into specific subdirectories. These subdirectories are then used (by MkDocs) at site creation to group the files into a collector on the lefthand navigation of the site generated. This makes it nice because you can easily group similar files in an area that is easily navigated.

Finally, here’s the main section of the script which executes the functions we’ve declared:

In order, they run the following:

  • delete_files_and_folders() — deletes any files and folders that were generated from the last run of the script
  • create_files_and_folders() — creates any files and folders that are necessary for copying and building the structure for MkDocs
  • select_md — selects the markdown files from the locally downloaded copy of your GitHub project
  • copy_md — copies the markdown files and writes their values into the markdown.yml file so that MkDocs can use the files and yaml to create the site

Using the NPM Scripts

So with the python script above working the last step is to create some npm scripts that automate this whole process. Our goal is to get this working in a way that one terminal command can do the whole thing.

If you open the package.json file, look at the “scripts” section. This is where I’ve built custom commands that npm will recognize if you’re in the project’s root directory. To run any of these scripts just open a terminal at the root directory and prefix them with npm run. So for my example for the script called “build” it could be run with npm run build.

Here are the scripts I used:

  • github-clone — clones the GitHub project you want to gather documentation from (in this case its Angular Material)
  • github-delete — deletes the local copy of your GitHub project
  • install-dependencies — installs MkDocs and the material theme with python’s pip (per the getting started guide)
  • build — builds the project and serves it locally
  • deploy — deploys the project to the repo’s GitHub pages site

So now, with all of this together, go to the root of the project and run the following:

npm run build and open your browser to http://http:localhost:8000 to see the following:

If you use the side navigation you can see where our copy_md() function has grouped the files into subfolders like so:

One of the best parts of MkDocs is that you can also use the search functionality to make finding documentation easy:

Finally, stop the terminal and run npm run deploy to push the changes to the GitHub Page’s site for the repo. When it finishes deploying you should see the following:

MkDocs will push the site to a gh-pages branch on your repo. This can be changed to a different branch and URL, but I’m just using the defaults here.

The GitHub Pages site where your MkDocs site is deploy to follows the convention of: https://<github_username><repo_name>

Closing Thoughts

So with this post I shared one way to use both MkDocs and Python to organize a project’s documentation. This can be shared, and creates a convenient way to showcase your documentation. The process I’ve setup here is still manual, but next steps would be to put this into a CICD pipeline. You could imagine running this whenever your project does a production release, or even on just whenever PRs get merged. If you use a Docker container with a CI system like Jenkins or CircleCI it makes all of this super easy. I hope you enjoyed learning about this, and can use this for some future projects.

Husband, Engineer, OSS Contributor, and Manager at CapTech Consulting. Follow me on and

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store