Generated from
fhir-harness/processes/tools/ig-docs-site-compose.bpmnbygen-processes-viz.ts— do not edit here. All processes · fhir-harness processes
Each IG, composed into a host docs site and rendered with just-the-docs
Process_IgDocsSiteCompose · advisory · 4 step(s)
How a host docs site builds every IG it mounts INSIDE itself, so each IG’s pages wear the host’s chrome (one sidebar, one search, one language selector) rather than being a site of their own. Subprocess of Tool stage-ig-sites; reached from docs-site-publish’s Call_InstanceSites (skill docs-generation).
NO IG PUBLISHER RUNS. build-ig-site turns the IG’s source into Jekyll source, with the Publisher’s site.data.fhir filled from the IG’s AST and sushi-config.yaml, and the host’s ONE Jekyll build renders it with just-the-docs (skill ig-render-jekyll). Which IGs is DATA: each instance whose fhir-artifact-index/menu.json records a source.of (the IG repository) and source.ref (the commit). No workflow and no step here names an IG.
feature-staging.yml runs the same steps for a pull request’s preview, with --changed-files, so only the IGs a change reaches are rebuilt. An IG repository building its OWN site runs stage-ig-sites --only <instance> --source <checkout> --compose-into <shell> --compose-at-root, which is ig-ast-cache’s Task_BuildSite, not this process.
How it connects
- Called by: no call activity names this process
- Calls: none
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Build each IG’s artefact indexTask_Indexes | Host docs site build (CI runner) | ig-build-pipeline | Tool ig-index-build: bun run cat ig-index:build. Restores each IG’s AST from its cache branch and writes fhir-artifact-index/ (index.json, menu.json with the source.of/source.ref that Task_Stage clones from, releases.json, package.tgz). A missing input skips that instance, named. |
Generate each IG instance’s artefact pagesTask_Pages | Host docs site build (CI runner) | ig-build-pipeline | Tool ig-pages: bun run fhir-harness/scripts/gen-ig-pages.ts --instance <instance> ..., run for every IG instance by its own pages script. Writes <instance>/docs/ from the artefact index: one thin page per artefact with its JSON-LD node, and, for an instance whose docs declare igSite, only a front-matter artifacts.md. Built at publish, never committed. |
Clone each IG at its recorded commit and stage itTask_Stage | Host docs site build (CI runner) | ig-render-jekyllig-build-pipeline | Tool stage-ig-sites: bun run fhir-harness/scripts/stage-ig-sites.ts --work ./_ig --baseurl /<repo> --plantuml-jar <jar>. Clones each IG at its recorded commit and stages ONE just-the-docs Jekyll source per IG with Tool build-ig-site (pages, includes, images, PlantUML, _data/, theme colours); the artefact lists (artifacts, toc) are thin pages over the artefact index node (Liquid only under --full-pages), and the instance’s artefact pages from Task_Pages are copied in. The theme is the one webpage theme the instance declares or inherits along needs; two at the same distance are refused. |
Compose each staged IG into the host sourceTask_ComposeInto | Host docs site build (CI runner) | ig-render-jekyll | Tool stage-ig-sites with --compose-into ./_docs (the same run as Task_Stage). Moves each staged site INTO the host’s Jekyll source at <instance>/, with its includes and data namespaced per IG. Pages wear the thin layout with the host’s chrome linked (--full-pages inlines the host’s full chrome instead). Prints one <instance> <jekyll source> <at> line per IG: the build list the host keeps (./_ig-list.txt) for the post-build pass. |