Say "student" and "profile" in the UI, not "child" and "family"

Sweep the translatable strings across the frontend templates, the admin screens, the editor previews and the block inserter entry. Nothing else moves: the database columns, request parameters, form field names, CSS classes, the us_family shortcode and the us-scheduler/family block name are contracts with existing installs and with post content people have already saved, so renaming them would break sites for no user-visible gain. Two strings are reworded rather than swapped, because the direct substitution reads wrong: - The students list said "Child of Jane" and now says "Managed by Jane". "Student of Jane" would read as a teacher's pupil, which is exactly the wrong idea in a music studio. - A managed account is now "a managed student account" rather than "a student account", which would not distinguish it from the account holder. The guardian feature doc gains a short section on the split, so the next person to work on it does not read the mismatch as drift and "fix" it. Closes #144 Co-Authored-By: Claude Opus 5 <[email protected]>
2026-07-29 20:34:55 -03:00
parent 8013d05d68
commit 76caf178f0
15 changed files with 66 additions and 47 deletions
@@ -88,8 +88,8 @@ All actions are nonce-protected POSTs handled on the detail page:
  `tests/Unit/Payment/PaymentRepositoryTest.php`

 ## Family Relationships
-The students list gains a **Family** column — a child links to their guardian,
-a guardian lists their children — and the student screen a **Family** panel. A
+The students list gains a **Profile** column — a child links to their guardian,
+a guardian lists their children — and the student screen a **Profile** panel. A
 child's listed email is their guardian's, since a child's own address is an
 undeliverable placeholder, and the credit balance shown is the payer's, labelled
 with whose account holds it. See `parent-guardian-accounts.md`.