Race Training Calendar

Live preview — the example content ships with the template and is replaced by your content.

What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.

Slots

Repeat: week (4–30×)

One calendar row per training week, in chronological order. Each row has a gutter cell plus seven day cells (Mon–Sun).

Repeat: away-session (1–6×)

One line per optional session in the away/travel block. Inside the away-block optional.

Repeat: exercise (3–12×)

One row per strength exercise. Inside the strength-log optional.

Optional blocks

• checkpoint-block — Decision rules after a mid-plan test race or time trial. Keep it only if the plan actually contains a test session; remove it otherwise.
• away-block — Menu of flexible sessions for travel days. Keep it only if the calendar contains 'day ev' travel days; remove it otherwise.
• strength-log — Final page: strength exercises × 15 week columns to write weights into. Remove it if the plan has no strength work.

The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).

This is a wall calendar, not a table of text — it is meant to be printed, ticked off with a pen and hung up. Fill it in this order.

1. HEADER. title-main + title-accent together are the race name (rendered uppercase, keep them short). plan-eyebrow states the block length and its first and last day. The four stat pairs are normally race day, goal time, goal pace and volume build (start → peak).

2. PACE ZONES. Derive the four zones from the goal time. The zones are the legend for the calendar's coloured bars, so keep their meaning: easy (sage), goal pace (rust), threshold (amber), interval (dark). Use one unit consistently everywhere — km or miles — including in every session and week target.

3. CALENDAR. Duplicate the 'week' row once per training week, in chronological order (min 4, max 30), and delete every data-example row. Per row: week-number is only the number ('wk' is fixed in the template); week-range is Monday–Sunday; week-target is the planned volume, which you compute as the sum of that week's sessions.

Every day cell has a class attribute slot ({day}-class) that drives its colour and layout. Use exactly one of:
  · 'day rest' — rest day or strength-only day. Tick box and write-in boxes are hidden automatically; the text renders small and italic ('Rest', 'Strength ~40 min').
  · 'day t-easy' — easy / recovery / long easy run (sage bar)
  · 'day t-quality' — tempo or threshold work (amber bar)
  · 'day t-interval' — intervals, repeats (dark bar)
  · 'day t-goal' — goal-pace work, including long runs finishing at goal pace (rust bar)
  · 'day t-test' — test race or time trial (blue, tinted cell)
  · 'day ev' — travel, holiday, wedding, festival: a day the plan works around. Put the event name in {day}-session; tick boxes hide automatically.
  · 'day t-race' — race day itself. Put the race name in {day}-note and '42.2 km · goal 4:00' style content in {day}-session.
Do not put anything else in these slots and do not invent class names.

Keep {day}-session under ~40 characters so the cell stays readable. {day}-note is the small rust flag above it ('long run', 'in race shoes', 'test gels and drinks', 'moved from Saturday') — leave it empty and it disappears, same for {day}-pace on rest and event days. {day}-date is the day of the month; add a short month name on the first of a month ('1 Sep').

Mark special weeks through week-class: 'gut g-recovery', 'gut g-peak', 'gut g-taper', 'gut g-test', 'gut g-event', 'gut g-race'. Ordinary weeks are just 'gut'. week-tag is the matching short label, or empty.

4. OPTIONAL BLOCKS. Remove checkpoint-block if the plan has no mid-plan test; remove away-block if there are no travel days; remove strength-log if there is no strength work. The strength log has 15 fixed week columns — for a longer plan, say so to the user rather than adding columns.

5. SANITY-CHECK THE PLAN before you deliver it: volume builds by roughly 10% per week, a recovery week every third or fourth week, hard days never back to back, the long run never the day after strength work, a real taper in the final two to three weeks, and the race in the last row. If the user's request implies an unsafe ramp, say so instead of printing it silently. This is a training aid, not medical advice — for injury, illness or a first marathon after a long break, suggest they check the plan with a coach or physio.

LANGUAGE: you may translate the fixed labels (weekday headers, 'week', 'logged', legend, panel headings) into the user's language, and should when the user's content is in that language. Never translate the class vocabulary — 'day t-goal', 'gut g-peak' and friends must stay exactly as written.

PAGE 1 PANELS: week-rhythm is a dl (dt = when, dd = what). key-principle is the one thing this athlete must not get wrong. back-off and practical are short ul lists. Keep page 1 to a single sheet: four zones, three columns, roughly 4 + 3 + 4 items.

Published versions are immutable: /t/race-training-calendar@{version}/ never changes once live. /t/race-training-calendar/ always points at the latest.