AREDN Documentation Repository
Go to file
Steve Lewis KC0EUW 2b736d4198 Include Win example TFTP client
Include another Windows TFTP client example for firmware image 
transfers.
2019-06-27 08:56:12 -07:00
_images Add AREDN logo to 2 pages 2019-02-20 11:09:17 -08:00
appendix Change TM to Registered Trademark symbol 2019-03-24 08:21:09 -07:00
arednGettingStarted Include Win example TFTP client 2019-06-27 08:56:12 -07:00
arednHow-toGuides Add clear browser cache to firmware install section (#34) 2019-06-14 13:55:20 -05:00
arednNetworkDesign Add clear browser cache to firmware install section (#34) 2019-06-14 13:55:20 -05:00
arednServicesGuide Clarify Mikrotik install steps 2019-04-03 08:13:40 -07:00
.gitignore Added .DS_Store back in for OSX environments 2019-01-22 17:18:08 -05:00
How to Use GitHub for AREDN.md Added How to Use GitHub doc 2018-12-21 10:00:25 -07:00
README.md Update README with another clarification 2019-01-19 13:39:25 -08:00
conf.py Change release number to final 3.19.3.0 2019-03-22 20:08:16 -07:00
index.rst Clarify Mikrotik install steps 2019-04-03 08:13:40 -07:00

README.md

AREDN Documentation

This repository is for creating documentation for the AREDN project so it can be made available on ReadTheDocs.

Viewing the Docs:

To view the AREDN documentation in a web browser, navigate to https://arednmesh.readthedocs.io/en/latest/ or select your choice from the Docs dropdown menu on https://arednmesh.org.

Exporting to PDF:

While viewing the AREDN documentation in your web browser, you will see the contents list in the left panel. At the bottom of the panel is a drawer labeled "ReadTheDocs" showing the version you are viewing. Click the label bar to open it. From the drawer you can export the documentation set as a single PDF or Epub file. This is handy if you want to take a PDF copy of the guidebook with you into the field where you do not have Internet access.

Contributing:

If you are interested in contributing to the rapidly growing set of AREDN related information, you can easily do so on GitHub. The workflow for contributing documentation is identical to the workflow for contributing code which is described in detail here: How to Use GitHub for AREDN.

The only difference is the repository name of aredn/documentation and the main branch name of master. Your local code branch name can be anything that makes sense to you. After you create your Pull Request, the AREDN team will review your request just as it does for code changes. Once your documentation contributions are committed to the AREDN GitHub repository, a webhook updates and builds the latest docs for viewing and exporting on ReadTheDocs.org

AREDN documentation is written using the reStructuredText markup language. Text is saved in "rst" files. Before committing your changes, be sure to test your rst files to ensure they will render correctly.