The problem
Recorded is not the same as explained
Garmin and Strava already capture the workout. What tends to be missing later is a calmer read: what the latest session means, how the week is shaping up, and what should follow next.
About
After the watch, before the next session
Training explained, not just recorded. This is the quiet reading layer on top of Pacer: static, personal, and built to stay useful after the workout is over.
Training explained Static-first Pi 5 to Pi Zero
What it is not
Not another training platform
run.nico.ar does not try to replace Garmin, Strava, or Pacer. It sits after them. The watch records. Pacer prepares the data. This site turns that export into a lightweight reading layer, with the current cycle kept in Runs and the older marathon site kept separate as Archive 2025.
How it fits
Pacer in, run out, e-ink later
Pacer
Handles the heavier aggregation work and produces the local dataset. It is the engine, not the public portal.
run.nico.ar
Surfaces the latest session, the shape of the week, and the next suggestion with much less friction than a full training app.
E-ink
Keeps a compact JSON output ready for a smaller display later, without adding server-side complexity now.
Static-first
Built for Pi 5 build time and Pi Zero serving
- Pacer exports local JSON on the Pi 5 side.
- run.nico.ar reads that snapshot, normalizes it, and adds a small layer of interpretation.
- Astro builds plain HTML, CSS, and /eink-summary.json for static hosting on the Pi Zero.
The tradeoff is deliberate: fewer moving parts, no production SSR, no live tokens in the frontend, and a result that stays easy to maintain. It also leaves room for richer Strava, lap, and block analysis later without rebuilding the whole site.