Updates range from fresh tzdata and copy edits to new specialist pages when a real team runs out of runway without them. We document specifics in internal notes; here you get the theme: constant sanding, fewer surprises.
What tends to improve
If something changes, it’s usually because one of these needed attention.
- Clearer guidance wherever results need interpretation or context.
- Edge-case fixes and accuracy improvements when offsets, calendars, or rolling windows get tricky.
- Simpler page structure and navigation so the important controls stay in view.
- Stronger supporting content on the Learn and Use-Cases pages when people keep asking “why does this work?”
- Seasonal or specialist pages only when they solve a real, time-bound problem.
Why there is not a giant release log
Most updates are incremental. You benefit more from quieter, steady improvements than from dramatic announcement posts. The goal is better tools, not a wall of version notes that nobody reads twice.
The short version
If a page, tool, or guide gets touched, it’s because it became more useful, clearer, or more accurate. The site is maintained continuously—just without startup fanfare.