{% extends "base.html" %} {% block title %}Calendar ยท {{ app_name }}{% endblock %} {# ๐Ÿ”ด THE COLOURS ARE THE DATA. Each pip is one activity in that activity's own colour, so a day's colours name WHAT was done โ€” strictly more informative than one channel of intensity-green, and it needs no palette decision because the colours are user rows. ๐Ÿ”ด THE `late` MARK IS LOAD-BEARING, NOT DECORATION. Latch has had a retroactive log since 0.2.0, so a backdated entry can repair a broken streak โ€” which is what the feature is for. But a grid that draws a repaired day identically to a lived one turns the retroactive log into a way to quietly rewrite history to yourself. The timeline already prints "โ†ถ logged later"; the calendar says it too. #} {% block body %}

๐Ÿ“… {{ cal.label }} what you did, in each thing's own colour

โ† prev today {# a month in the future has nothing in it and a stepper that walks into empty grids forever reads as a bug โ€” the link is simply absent past the current month. #} {% if cal.has_next %}next โ†’ {% else %}next โ†’{% endif %}
{% for d in ("Mon","Tue","Wed","Thu","Fri","Sat","Sun") %}{{ d }}{% endfor %}
{% for week in cal.weeks %}
{% for d in week %}
{{ d.dom }} {% if d.acts %}
{% for a in d.acts %} {% endfor %}
{% endif %}
{% endfor %}
{% endfor %}
{% for a in cal.activities %} {{ a.icon }} {{ a.title }} {% endfor %} โ†ถ logged later
{% if not cal.activities %}

No activities yet โ€” add one in Settings and this fills in from the log you already have.

{% endif %}
{% include "_acts.html" %} {% endblock %}