Documentation Update Guide

Set-up

1. Clone the documentation repository
   • git clone https://github.com/theicct/polaris-doc.git
   • This is a public repository – do not commit any code or sensitive information!
2. Make sure you have access to the latest version of the shared Word document

Dependencies

1. gh-md-toc
2. pandoc version 2.10.0 - install with conda install -c conda-forge pandoc=2.10.0
3. (Optional) Install a Markdown editor
4. (Optional) Install Jekyll if you intend to test the documentation changes locally

Updating the documentation

1. Write your updates in the Word version
2. Get review from the team, as necessary
3. Save as a .pdf file to the versions folder with the name Polaris vX.Y Model Documentation.pdf where X and Y reference the model version, e.g. Polaris v1.6 Model Documentation.pdf (make sure you hide all markup before exporting)
4. If you added images to the Word document, add them to the assets folder
5. Copy your changes to a Markdown version of the documentation either manually or automatically
   • 5a. Copy manually
     • Make a copy of the latest Markdown version of the documentation, using the same naming convention (for example, if the latest documentation is v1.5.md, create a copy named v1.6.md, matching the version of the Roadmap model)
     • Add your changes to the new Markdown file using your favorite Markdown editor
     • If you added images in step 4, add them to the file by inserting the following in the document: ![](/polaris-doc/assets/[filename]) where [filename] is the name of the image
   • 5b. Copy automatically
     • Edit the file path in shared_version.sh to point to the Word version
     • If you added images in step 4, update the IMG_MAP in doc_to_page.py
     • Run the copy_doc.sh bash script
       • If you get a /bin/sh: gh-md-toc: command not found error, try reinitializing basher first with export PATH="$HOME/.basher/bin:$PATH" and eval "$(basher init - zsh)"
     • Open up the Markdown doc (versions/vX.Y.md) and manually add line breaks ("\\") to make multiline equations if needed
6. (Optional) Test your changes locally
   • First, temporarily remove all references to the /polaris-doc directory (it becomes the baseurl once served by GitHub) from the Markdown documentation file and the _config.yml file
   • run jekyll serve
   • Make sure you add back in the references to /polaris-doc
7. Add and commit the new documentation files
   • git add versions/vX.Y.md versions/Polaris vX.Y Model Documentation.pdf
   • git commit -m "[Useful description of changes]"
8. Push your changes, wait a minute, then check to make sure the online version updated correctly