GitHub "Use this template" scaffold for new hardware module repositories under OE5XRX. New modules cloned from this template start pre-wired to the shared CI infrastructure at OE5XRX/HW-Module-CI.
- Click "Use this template" on GitHub to create a new module repo (e.g.,
HW-Module-Acme). - Clone the new repo locally.
- Replace
LICENSEif your license differs from CERN-OHL-S 2.0. - Create your KiCad project at the repo root. The
.kicad_pro,.kicad_sch, and.kicad_pcbcan be named anything — the shared CI auto-detects the basename. Convention: name them after the module (e.g.,Acme.kicad_pro). - Fill in
doc/index.md:- Replace
<NAME>with the module's display name (e.g.,Acme). - Update
nav_orderto position it correctly on the hardware overview page. - Replace
Some Textwith the module description, voltage tables, etc. - Output paths already use
{{ site.data.project.name }}— leave those as-is; CI fills in the auto-detected KiCad basename at build time.
- Replace
- Commit and push. On the first push to
main, CI auto-runs:KiBot Check— ERC + DRC preflightCreate Debug Docs— publishes preview to the repo'sgh-pagesbranch
- On the first GitHub release:
Create Release Docsdeploys versioned docs toOE5XRX.github.ioand pushes BOM to InvenTree.
.github/workflows/— 3 thin wrappers thatuses: HW-Module-CI@maindoc/index.md— Jekyll page scaffold (replace<NAME>+ content)3d-models/,symbols/,footprints/— empty subdirs for optional KiCad librariesLICENSE— CERN-OHL-S 2.0README.md— this file (overwrite for your module)
KiBot configs, Python scripts (BOM export, InvenTree sync, stencil PNG), Jekyll config, Gemfile, doc assets (favicon, logo) — all of these live in OE5XRX/HW-Module-CI and are pulled in at CI-runtime. Do not copy them here.
CERN-OHL-S-2.0 by default; replace LICENSE if your module needs a different license.
OE5XRX Amateur Radio Club
🌐 https://oe5xrx.org
✉️ info@oe5xrx.org