Skip to content

Alex-McVey/MHKiT

 
 

Repository files navigation

How to Update the MHKiT Documentation Website

The MHKiT documentation is developed as restructured text files that are compiled by Sphinx into html files and then uploaded to the MHKiT Documentation Repository. Using Sphinx, GitHub renders the documentation on the MHKiT Documentation Repository as the MHKiT Documentation Website. This guide will help the user to download the documentation, modify the documentation, build the documentation locally, and push changes back up to the repository.

Requirements

To update the MHKiT documentation you will need Python 3.6+, Git, Sphinx, and a GitHub account. This documentation assumes the user has a working version of Python installed (We recommend Anaconda Python, during installation check the add Python to Path) and a GitHub account but will cover the needed Python Sphinx package installation.

Step 1. Fork the Repository & Clone to local machine

  • To update the documentation a user will need to "fork" this repository. This simply means that you are creating your own copy of this repository that you can edit.
  • Once forked you can "clone" (this will download your fork to your machine) the repository to your local machine using the command line.
  • Using the command line navigate to the file system location you would like to keep the documentation repository clone the documentation. Replacing the username and repository name to the correct values for you. This link can be automatically generated on your fork by copying the link visible after clicking clone on your repository page. The repository name will be assumed to be MHKiT in the remaining commands.
  git clone https://github.com/USERNAME/REPOSITORYNAME.git
  • Once cloned use the command line to change directories into the folder created by the clone to update the MHKiT-Python and MHKiT-MATLAB [submodules].
   cd MHKiT
   git submodule init
   git submodule update --remote

The MHKiT-Python and MHKiT-MATLAB folders should now contain source code.

To build the Python API documentation for submitting a pull request you will want to use the submodule MHKiT-Python included here. To do so first uninstall any MHKiT you may have and then use the python package manager to install this MHKiT submodule.

pip uninstall mhkit
cd MHKiT-Python
pip install .

NOTE: After building the documentation (see below) be sure to reinstall your MHKiT-Python distribution from pypi (e.g. pip install mhkit) or from your fork of the repository as an editable package (e.g. pip install -e /path/to/my/fork/of/MHKiT-Python)

Step 2. Download/Install Sphinx package and extensions

  • Sphinx is a python package used to create the MHKiT documentation.

  • Install Sphinx from the command line NOTE: You may need to add PROXY settings (see info here)

    pip install -U Sphinx

    • Sphinx --> Version: 3.1.1
  • Use the command line to install the needed Sphinx submodules (BibTex, MATLAB theme, rtd theme, and NB Sphinx)

    pip install -U sphinxcontrib-bibtex sphinxcontrib-matlabdomain sphinx_rtd_theme nbsphinx

    • nbsphinx --> Version: 0.7.1

    • sphinxcontrib-matlabdomain --> Version: 0.11.2

    • sphinxcontrib-bibtex --> Version: 1.0.0

    • sphinx-rtd-theme --> Version: 0.5.0

You are now ready to begin modifying and building the MHKiT documentation.

Step 3. Modify the Documentation

  • The restructured text files used to build the documentation are located in the /MHKiT/docs/source directory (Check the Sphinx Website for information about the folder structure).
  • Before modifying the documentation we recommend creating a feature branch and not modifying your fork's master branch. A feature branch can be created using the commands
git branch featureBranchName
git checkout featureBranchName
  • Now you can use a text editor to modify any restructured text file (files with .rst extension, e.g. index.rst).
  • Once you are done editing, move to Step 4

Step 4. Build the MHKiT Documentation

  • To locally build the documentation use the command line to move into the /MHKiT/docs folder then make html
    cd docs
    make clean
    make html

Using your machine's file explorer navigate to MHKiT/docs and use an Internet browser (i.e. Chrome, Safari, Edge, etc. ) to open index.html to view modifications to the documentation source made above.

Step 5. Update to the MHKiT Documentation

  • Once changes have been made the user can push the changes back up to their fork

    git status
    • The status will return a list of files that have been modified. If you want to commit all of the changed files you can use git add --all otherwise use git add fileName where fileName is either the file or a list of space-separated files the user wishes to add.
    • Commit the changes with a message documenting what has been changed
    git commit -m 'A descriptive message here describing why or what was changed in the documentation'
    
    • Finally, push the changes to your fork's (yourFork) feature branch (featureBranchName).
    git push -u yourFork featureBranchName
    
    • If you did not create a feature branch simply type git push

Step 6. Submit a Pull Request

Best Practices

  • Run spell check (not built into most text editors)
  • Update the MHKiT-Python and MHKiT-MATLAB submodules git submodule init git submodule update --remote, refer to https://git-scm.com/book/en/v2/Git-Tools-Submodules for more information
  • When compiling the website, make clean and then make html

Formatting Guidelines

Terminology Guidelines

  • DataFrame (not dataframe)
  • MATLAB (not Matlab)
  • Python (not python)
  • pandas (not Pandas)
  • MHKiT (not mhkit)
  • open-source (not open source)
  • time-series (not timeseries or time series)
  • time-domain (not time domain)
  • frequency-domain (not frequency domain)
  • MHKiT-Python (or link to MHKiT-Python when referring to the repo)
  • MHKiT-MATLAB (MHKiT-MATLAB when referring to the repo)
  • MHKiT (Marine and Hydrokinetic Toolkit)

Releases

No releases published

Packages

No packages published