feat: merge event rankings and attribute badges into the page printer

Interview notes can print each student's ranked events and a shared attribute legend from the same catalog as the ranking index, without leftover table markup or collapsed answer space. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-30 23:03:10 -04:00
parent 3f50d6e635
commit 3712dba974
19 changed files with 817 additions and 118 deletions
@@ -21,13 +21,44 @@ Create a standalone note on **Notes** (not a page note or student note). Use `{{

 1. Why did you join TSA?
 2. What events interest you?
+
+**Event preferences**
+
+| 1st | 2nd | 3rd | 4th | 5th | 6th |
+| --- | --- | --- | --- | --- | --- |
+| {{Rank1}} | {{Rank2}} | {{Rank3}} | {{Rank4}} | {{Rank5}} | {{Rank6}} |
+| {{Rank1.Attributes}} | {{Rank2.Attributes}} | {{Rank3.Attributes}} | {{Rank4.Attributes}} | {{Rank5.Attributes}} | {{Rank6.Attributes}} |
+
+{{Legend}}
 ```

-Unknown tokens stay visible so typos are obvious. Empty values (including a missing Interview Time) print blank.
+Or use `{{RankedEvents}}` for the ranking-index badge row instead of the table.
+
+Unknown tokens stay visible so typos are obvious. Empty values (including a missing Interview Time or an unset rank) print blank.
+
+Student pages also have event-rank tokens from **Student Event Ranks**. See [event-ranking-import.md](event-ranking-import.md).
+
+- `{{RankedEvents}}` prints that student’s preferences as ranking-index badges (colored rank dot, short name, attribute marks).
+- `{{Rank1}}` through `{{Rank10}}` print the official event name at that preference.
+- `{{Rank1.ShortName}}` / `{{Rank1.Attributes}}` (through 10) print the catalog short name and the same attribute marks shown on **Student Event Ranks** (level of effort, individual, on-site, regional, presubmission).
+
+Event pages can put the matching student list under the event name:
+
+```markdown
+# {{Name}}
+
+{{EventAttributes}}
+
+{{RankedStudents}}
+```
+
+`{{RankedStudents}}` prints everyone who ranked that event as badges (colored rank dot and first name), same sort as **Events by Student** on the ranking index: rank, then grade + TSA year. `{{EventAttributes}}` is also available on team pages.
+
+Put `{{Legend}}` where you want the attribute-mark key (same marks as the Teams printout legend).

 Put `{{PageBreak}}` on its own line to force a new printed sheet **inside** one record (for example, questions on page 1 and a scoring rubric on page 2).

-Put `{{AnswerSpace}}` where you want ruled write-in lines. Markdown collapses blank lines, so extra empty lines in the note will not leave room to write.
+Put `{{AnswerSpace}}` where you want ruled write-in lines. Markdown collapses blank lines, so extra empty lines in the note will not leave room to write. **Answer lines** on the printer page sets the height of each token; add another `{{AnswerSpace}}` to stack a second block.

 Additional-field tokens use the same names as the Students index columns (for example `{{Interview Time}}`). Those values come from each student's `#Student:{id}` `## Additional fields` table. See [student-notes-import.md](student-notes-import.md).

@@ -11,4 +11,7 @@ User-facing steps: [docs/instructions/page-printer.md](../instructions/page-prin
 - Core merge: `{{tokens}}`, `{{PageBreak}}`, `{{AnswerSpace}}`, print presets JSON
 - `/print` UI: entity filters, font size, answer-space lines, Preview/Print, save/load/update/delete presets
 - Student pages sort by last name, then first name
+- Student event-rank tokens: `{{Rank1}}`–`{{Rank10}}`, `.ShortName` / `.Attributes`, and `{{RankedEvents}}` badges
+- Event `{{RankedStudents}}` badges (students who ranked the event) and `{{EventAttributes}}`
+- `{{Legend}}` from the shared attribute-mark catalog (`EventAttributeMarks`)
 - EF migration `AddPrintPresets` (applied on next app start)