CodingNotes is a Sphinx and Jupyter Book documentation site containing practical notes on command-line tools, HPC, Python, molecular simulation, and scientific software.
Published site: https://van-richard.github.io/CodingNotes/
Clone the repository:
git clone https://github.com/van-richard/CodingNotes.git
cd CodingNotesconda create --name codingnotes python pip
conda activate codingnotes
python -m pip install --upgrade pippython3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pippython -m pip install -r requirements.txtTo deploy with build.sh, also install ghp-import:
python -m pip install ghp-importBuild the HTML documentation locally:
sphinx-build . _build/htmlOpen _build/html/index.html in a browser to inspect the result.
GitHub Actions builds the documentation for pull requests and automatically deploys _build/html to GitHub Pages after changes are pushed to main. The workflow is defined in .github/workflows/pages.yml.
In the repository settings, configure GitHub Pages to use GitHub Actions as its source.
For a manual deployment, build.sh remains available. It builds the site and publishes _build/html with ghp-import:
./build.shBefore running it, activate the project environment, install ghp-import, and ensure the working tree is ready to publish. The script also updates _external/amberassist when that optional repository is available and pushes the generated site, so it should be treated as a deployment command rather than a local build command.
index.md: site landing pagenotebooks/: authored Markdown pages and Jupyter notebooksstatic/and_static/: images, videos, scripts, styles, and other static resourcesassets/: custom CSS, JavaScript, and HTML theme templates_toc.yml: external table-of-contents configurationconf.py: Sphinx configurationrequirements.txt: Python documentation dependenciesbuild.sh: build and GitHub Pages deployment script.github/workflows/pages.yml: automated documentation build and Pages deployment_build/: generated documentation outputjupyter_execute/: generated notebook execution artifacts
- Keep authored content and source assets tracked in Git.
- Do not commit
_build/,jupyter_execute/, doctrees, notebook checkpoints, or local virtual environments. - Update
_toc.ymlwhen adding, moving, or removing documentation pages. - Run a clean local build before deployment and review all Sphinx warnings.
- Verify external files referenced from
_external/amberassistare available before building pages that useliteralinclude.