Band Lineup's docs move to where every other module's live #21

Merged
christian merged 1 commits from claude/band-lineup-docs-tidy into main 2026-09-24 11:31:11 -04:00
Collaborator

Two things were out of place.

modules/band-lineup/README.md was the only README inside any of the eight modules. The guide's folder shape is manifest, client, server, assets — and every other module is described in the repo README's Included modules instead. It was also documenting a module that no longer exists: photos and birthdays "come from Planning Center", guests "pinned per slot" from Edit, and a refresh interval the manifest has never had. That was the 1.10.0-era design.

The repo README's entry had drifted the same way — calling the Drive folder somewhere to put "manual photos", and the board something Planning Center fills. It is the other way round, and has been since 1.10: the board is shared server state and the source of truth, the photo library (a Drive folder or a local path, kept in sync) fills it, and Sync is auto-fill that only touches slots nobody placed by hand. The corrected entry says that, and picks up the Choir spot and the title-bar columns while it's there.

Net: one stale file removed, one accurate description in the place the guide says documentation goes.

Nothing in the module's code changes — modules/band-lineup/ is otherwise untouched at 1.11.0, and its id matches its folder name.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

Two things were out of place. **`modules/band-lineup/README.md` was the only README inside any of the eight modules.** The guide's folder shape is manifest, client, server, assets — and every other module is described in the repo README's *Included modules* instead. It was also documenting a module that no longer exists: photos and birthdays "come from Planning Center", guests "pinned per slot" from Edit, and a refresh interval the manifest has never had. That was the 1.10.0-era design. **The repo README's entry had drifted the same way** — calling the Drive folder somewhere to put "manual photos", and the board something Planning Center fills. It is the other way round, and has been since 1.10: the board is shared server state and the source of truth, the photo library (a Drive folder or a local path, kept in sync) fills it, and Sync is auto-fill that only touches slots nobody placed by hand. The corrected entry says that, and picks up the Choir spot and the title-bar columns while it's there. Net: one stale file removed, one accurate description in the place the guide says documentation goes. Nothing in the module's code changes — `modules/band-lineup/` is otherwise untouched at 1.11.0, and its `id` matches its folder name. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
christian added 1 commit 2026-09-24 11:30:42 -04:00
Two things were out of place. `modules/band-lineup/README.md` was the only
README inside any of the eight modules — the guide's folder shape is manifest,
client, server, assets, and every other module is described in this README's
*Included modules* instead. It was also describing a module that no longer
exists: photos and birthdays "come from Planning Center", guests "pinned per
slot", and a refresh interval the manifest has never had.

The entry here had drifted the same way, calling the Drive folder somewhere
to put "manual photos" and the board something Planning Center fills. It is
the other way round now, and has been since 1.10: the board is shared server
state and the source of truth, the photo library fills it, and Sync is
auto-fill that only touches slots nobody placed by hand. The entry says that,
and picks up the Choir spot and the title-bar columns while it is there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
christian merged commit a1ea9262c6 into main 2026-09-24 11:31:11 -04:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: michael/ProdDash#21