farmOS is a web-based application for farm management, planning, and record keeping. It is developed by a community of volunteers and aims to provide a standard platform for farmers, developers, and researchers to build upon
Go to file
Paul Weidner ce26a2bdee Remove abandoned Ansible farmOS project.
Appears that this repository no longer exists.
2021-06-01 11:00:02 -04:00
.github Automate Mkdocs GitHub Pages build process #73 2020-02-25 14:41:05 -05:00
docs Remove abandoned Ansible farmOS project. 2021-06-01 11:00:02 -04:00
.gitignore Initial commit of farmOS documentation. Just the basic mkdocs file infrastructure and a blank index page. 2016-01-13 08:32:08 -05:00
README.md Add mkdocs-bootstrap and mkdocs-bootswatch to the pip install command for initial setup of this repo. 2018-12-05 11:12:15 -05:00
mkdocs.yml Quick Weight form page created 2020-11-25 12:14:01 -05:00
requirements.txt Automate Mkdocs GitHub Pages build process #73 2020-02-25 14:41:05 -05:00

README.md

farmOS.org

This repository contains all the code and content used to build http://farmOS.org.

It uses mkdocs to convert simple markdown files into static HTML files.

To get started contributing to this project, fork it on Github. Then install mkdocs and clone this repo:

$ brew install python                # For OSX users
$ sudo apt-get install python-pip    # For Debian/Ubuntu users
$ sudo pip install mkdocs mkdocs-bootstrap mkdocs-bootswatch
$ git clone https://github.com/farmOS/farmOS.org.git farmOS.org
$ cd farmOS.org
$ git remote add sandbox git@github.com:<username>/farmOS.org.git
$ mkdocs serve

Your local farmOS.org site should now be available for browsing: http://127.0.0.1:8000/. When you find a typo, an error, unclear or missing explanations or instructions, hit ctrl-c, to stop the server, and start editing. Find the page youd like to edit; everything is in the docs/ directory. Make your changes, commit and push them, and start a pull request:

$ git checkout -b fix_typo              # Create a new branch for your changes.
...                                     # Make your changes.
$ mkdocs build --clean; mkdocs serve    # Go check your changes.
$ git diff                              # Make sure there arent any unintended changes.
...
$ git commit -am "Fixed typo."          # Useful commit message are a good habit.
$ git push sandbox fix_typo             # Push your new branch up to your Github sandbox.

Visit your fork on Github and start a Pull Request.

For more information on writing and managing documentation with mkdocs, read the official mkdocs documentation: http://www.mkdocs.org