Developing
Motivation
This documentation is designed to be a guide to our open source rover projects. It has been seperated from the main repoitory as it contains information about our team, past rovers and their iterations. These docs are contained in their own repo and managed with devenv.sh for a self contained reproducable environment.
Maintenence
Material for MkDocs is Abandoned
Project Dependencies
Minimal maintence in the ways of dependency management is required as Material for MkDocs is abandoned and will only be recieving security updates and major bug fixes. The Material for MkDocs dev team has moved onto a new project called Zensical which, when out of beta, should be a very easy direct replacement to Material for MkDocs.
GitHub Actions
The GitHub action workflow is based on two example workflows:
- The example for deploying a static website to github pages which can be found in the last section of this article from GitHub
- The devenv.sh example for automatically building projects
MkDocs does have the command mkdocs gh-deploy which has not been used as it does not have much documentation and is not trusted primarily due to Material for MkDocs being abandoned.
Last update
The actions used in the documentation workflow are up to date as of 07/10/26
Development Instructions
This project is managed by devenv.sh, which must be installed prior to running the project.
Installing required tools
| Packet Manager | Steps |
|---|---|
| apt | Install git using: sudo apt update && sudo apt install git. Check the devenv getting started page to find the appropriate installation method for your system (all of which require Nix). |
| Nix | You need the packages git and devenv. Add them to your system config for NixOS or enter a shell with them using nix-shell -p git devenv. |
Development Steps
Assuming devenv.sh and git are installed development should typically follow the steps (Assuming you are in your home directoy):
Setup
- Clone the repository with
git clone https://github.com/ROAR-QUTRC/roar-docs.git cdinto the cloned repo:cd ~/roar-docs- If this is your first time then you will need to allow devenv by running
devenv allow - Finally, if devenv does not automatically start cd out
cd ..and back into the repocd roar-docsand you should see devenv building the environment
Not sure if it worked?
When you change direcotry you should see an output similiar to this one:
✓ Validating lock 17ms
✓ Configuring shell 12ms
└ ✓ Configuring cachix 2ms
└ ✓ Evaluating shell cached 6ms
✓ Loading tasks 1ms
└ ✓ Evaluating devenv.config.task.config cached 0ms
✓ Running tasks 21ms
└ ✓ devenv:enterShell 9ms
└ ✓ devenv:files:cleanup 9ms
└ ✓ devenv:enterTest skipped 0ms
Development
cdinto the repository and wait for the devenv shell to load- Open the reposity in your favourite IDE (VS Code is recommended)
- Start the development server by running the command
devin the devenv shell and view the locally hosted website athttp://127.0.0.1:8000 - Create or edit content following the guides in Adding Content
- Once you make a new file or save changes you should be able to see live updates