| Repo Name | Purpose | Status |
|---|---|---|
DEV.supplement-template |
Template for new Supplement documents (AsciiDoc + CI/CD) | To build |
Must have "Template repository" checked in Settings → General.
| Repo Name | Purpose | Notes |
|---|---|---|
DEV.documentation |
Documentation, governance, onboarding guides. | The "how everything works" hub. Plain Markdown — GitHub renders it natively. Anyone can edit via the web UI. |
DEV.tooling |
Planning docs, shared GitHub Actions, Asciidoctor build scripts, reusable workflows. Also contains proto-directories for other repos during bootstrapping. | Referenced by template workflows via uses: IHE/DEV.tooling/... |
| Repo Name | Purpose | Status |
|---|---|---|
| (existing TF repo) | Devices Technical Framework (already exists) | No migration needed |
DEV.{supplement-name} |
Individual supplement repos, created from DEV.supplement-template |
Created on demand |
DEV.whitepapers |
White papers (maybe) | TBD |
DEV.{name}
Examples:
DEV.supplement-template— the supplement templateDEV.wia— a supplement called "WIA"DEV.sdpi— a supplement called "SDPi"DEV.documentation— the documentation site
- No FHIR IG template or tooling
- No CP template — CPs will be handled differently (TBD)
- No Technical Framework template (the TF repo already exists)
- No repos for other IHE domains (ITI, PCC, RAD, etc.)
- No automated repo creation workflows
- No AsciiDoc theming (for now)