Skip to content

jbeechb/tier2-safe-docs

 
 

Repository files navigation

Tier-2 SAFE Documentation

This repository contains the documentation for the Tier-2 service management web interface (SAFE_ and is linked to a rendered version on ReadTheDocs.

For a guide on the rst file format see this document.

This documentation is drawn from the Sheffield Iceberg documentation and the ARCHER documentation.

I added some text here.

Rendered Documentation

Two versions of the documentation are currently automatically built from this repository:

How to Contribute

To contribute to this documentation, first you have to fork it on GitHub and clone it to your machine, see Fork a Repo for the GitHub documentation on this process.

Once you have the git repository locally on your computer, you will need to install sphinx to be able to build the documentation. See the instructions below for how to achieve this.

Once you have made your changes and updated your Fork on GitHub you will need to Open a Pull Request.

Building the documentation on a local Windows machine

Install the following:-

To build the HTML documentation run:

make html

If you want to build the PDF documentation you will need:

Then from the command line, the following will build the .pdf file

make latexpdf

On first run, MikTeX will prompt you to install various extra LaTeX packages.

Building the documentation on a local Linux machine

Have

  • Python 2
  • sphinx

installed, then run

make html

Building the documentation on a local Mac machine

For the HTML documentation you will need sphinx. If you do not already have a python distribution installed, we recommend you install Anaconda Python.

To build the HTML documentation run:

make html

Making Changes to the Documentation

The documentation consists of a series of reStructured Text files which have the .rst extension. These files are then automatically converted to HTMl and combined into the web version of the documentation by sphinx. It is important that when editing the files the syntax of the rst files is followed. If there are any errors in your changes the build will fail and the documentaion will not update, you can test your build locally by running make html. The easiest way to learn what files should look like is to read the rst files already in the repository.

About

Documentation for the Tier-2 SAFE hosted by EPCC

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 42.2%
  • HTML 32.9%
  • CSS 11.8%
  • Python 5.5%
  • Makefile 3.9%
  • Batchfile 3.7%