Skip to content

docs: flatten facilities, generate asset binding, tabulate TomoWise specs#291

Open
xmap wants to merge 2 commits into
mainfrom
worktree-facilities-flat-generated
Open

docs: flatten facilities, generate asset binding, tabulate TomoWise specs#291
xmap wants to merge 2 commits into
mainfrom
worktree-facilities-flat-generated

Conversation

@xmap

@xmap xmap commented Jun 21, 2026

Copy link
Copy Markdown
Owner

Summary

Two related docs simplifications for the deployments section.

1. Facilities flatten + descriptor-generated asset binding

  • The per-site assets.md was the only hand-authored facility page; everything it carried (beamline root-Asset binding, tier, facility_code) is already in site.yaml. Folded it into the generated index page (_modeled() in scripts/site_pages.py) and deleted the hand-authored files. The whole facility surface is now descriptor-generated.
  • Nav drops a level: Facility envelope > APS > {index, Assets} becomes a flat Facilities > APS / MAX IV (single leaves).
  • deployments/index.md retires the "facility envelope" framing for "facilities" and drops the scope-levels table now that each facility page carries its Asset binding inline.

2. TomoWise equipment tables + vocabulary clarifier

  • Converted the endstations.md and detector.md hardware enumerations from bullets to per-section spec tables (component, family, key specs, model/status), matching the generated pages and 2-BM. Connective prose kept.
  • Clarified that an endstation is an equipment grouping label, not a modeled aggregate; the access-gated hutch is the Enclosure on a separate axis. No rename: Enclosure stays the domain term, endstation stays informal. controls.md (prose) and equipment/index.md (linked overview) left unchanged.

Verification

  • make docs-build (mkdocs build --strict): exit 0; new Enclosure-module link resolves; no warnings touch the changed pages.
  • pytest tests/unit/deployments/test_site_descriptor.py: 11 passed (asserts the binding table is folded in and assets.md is no longer referenced).
  • Rendered HTML: endstations 2 tables, detector 3 tables; nav shows "Facilities", "Facility envelope" gone.

🤖 Generated with Claude Code

xmap and others added 2 commits June 21, 2026 22:35
…site descriptor

The facility surface had one hand-authored page left: per-site assets.md.
Everything it carried (the beamline root-Asset binding, tier, facility_code)
is already in the site descriptor, so fold it into the generated index page
and delete the hand-authored files. This makes the whole facility surface
descriptor-generated from site.yaml, and lets the nav drop a level: the
"Facility envelope" group becomes a flat "Facilities" with APS and MAX IV as
single leaves instead of each owning an Assets sub-page.

deployments/index.md retires the "facility envelope" framing for plain
"facilities" and drops the scope-levels table now that each facility page
carries its own Asset binding inline.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…on from enclosure

The TomoWise endstations and detector pages listed hardware as bullets while
the generated pages (inventory, beamline, site) and 2-BM use tables inside
framed sections. Convert the per-station and per-detector enumerations to spec
tables (component, family, key specs, model/status) and keep the connective
prose. Also clarify that an endstation is an equipment grouping label, not a
modeled aggregate: the access-gated hutch is the Enclosure on a separate axis.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant