Contributing to the documentation page

Contributing to the documentation page#

For Users

If you find mistakes in the page, please report it using Issues page. Please mention topics you think are missing, incorrect, or aren’t structured appropriately. If you want to get more actively involved, make a fork, implement you changes, and submit a pull request.

For staff

Please add yourself as members of this repository, and make changes to a branch in your name. Once changes are made, submit a pull/merge request to the main branch.

Structure of the source#

This website is created using Jupyterbook, based on sphinx. See the Jupyterbook for more details. The source for this website uses MyST Markdown.

The structure of the files looks like follows -

(web) πŸ‘½ 618-rajarshi 0 (main)βœ—  tree .
.
β”œβ”€β”€ README.md
β”œβ”€β”€ _config.yml
β”œβ”€β”€ _static
β”‚   └── style.css
β”œβ”€β”€ _toc.yml
β”œβ”€β”€ contact-us.md
β”œβ”€β”€ index.md
β”œβ”€β”€ interim-service.md
β”œβ”€β”€ logo.png
β”œβ”€β”€ lxp
β”‚   └── introduction.md
β”œβ”€β”€ national-hpc-service.md
β”œβ”€β”€ references.bib
β”œβ”€β”€ requirements.txt
└── scratch.md
...

There are three types of files

  • YAML files, with extension .yml which are used to define structure and build process of the pages. _config.yml file defines all the configurational options for building the pages, and _toc.yml file defines the table of contents, and structure of the documents.

  • CSS files, primarily stored in _static folder, and define the appearance settings for the webpages.

  • Markdown files, with .md extension. These are primarily ones that contain the documentation information. Jupyterbook follows MyST format, which is quite feature rich for building pages and pdfs of the technical documents. Checkout the MyST features here.