{#
  The dashboard.

  The page itself owns the header, the configuration warnings and the grid; each
  card owns everything inside it. Which cards there are, and in what order, is
  `fort.set_dashboard(...)` -- so this template never learns the name of a
  widget, and a project's own widget renders exactly like a built-in one.
#}
{% extends "base.html" %}

{% block content %}
  <div class="ff-page-header">
    <div class="ff-page-header__text">
      <h1 class="ff-h1">{{ _(settings.project_name) }}</h1>
      <p class="ff-muted ff-mt-2">
        {% if models %}
          {{ _("{count} model registered", count=models) if models == 1
             else _("{count} models registered", count=models) }}
          · {{ dialect }}
        {% else %}
          {{ _("Nothing registered yet") }}
        {% endif %}
      </p>
    </div>

    {#
      The window every card on the page covers.

      Links carrying `?days=`, not buttons and not a <select> that needs script
      to submit: the whole admin works with scripting off, and this is a
      navigation -- it changes what the page shows and belongs in history, so
      the back button does what anybody would expect. The server checks the
      number against `admin.dashboard_ranges` and falls back silently, so the
      only values that ever reach a widget are ones the deployment allowed.

      Rendered only when there is a choice to make: one window is not a choice,
      and a single dead tab is worse than no control.
    #}
    {% if ranges|length > 1 %}
      <nav class="ff-range" aria-label="{{ _("Days") }}">
        {% for option in ranges %}
          {#
            The visible text is the bare number, because three options reading
            "Last 30 days" each is a control wider than the heading above it.
            The whole sentence goes in the label, so what a screen reader hears
            is the sentence and not a stray "30" -- and both come out of
            catalogue entries that already existed, so a compact control cost
            no new translation in eleven languages.
          #}
          <a
            class="ff-range__option"
            href="?days={{ option }}"
            aria-label="{{ _("Last {days} days", days=option) }}"
            {% if option == days %}aria-current="page" {% endif %}
          >{{ option }}</a>
        {% endfor %}
      </nav>
    {% endif %}
  </div>

  {% if issues %}
    {# Configuration problems belong on the first page someone opens, not in a
       log they will not read. #}
    <div class="ff-alert ff-alert--warning ff-mt-0">
      <div>
        <div class="ff-alert__title">{{ _("Configuration needs attention") }}</div>
        <ul class="ff-mt-2">
          {% for issue in issues %}
            <li>{{ issue }}</li>
          {% endfor %}
        </ul>
      </div>
    </div>
  {% endif %}

  {% if cards %}
    <div class="ff-dash ff-mt-6">
      {% for card in cards %}
        {# The span is the widget's own, and it is a small integer from a
           constant in `admin/dashboard.py` -- never a number from a request. #}
        <div class="ff-dash__cell ff-dash__cell--{{ card.span }}">
          {% include card.template %}
        </div>
      {% endfor %}
    </div>
  {% else %}
    <div class="ff-card ff-mt-6">
      <div class="ff-empty">
        <div class="ff-empty__icon" aria-hidden="true">{{ ff_icon("database", size=22) }}</div>
        <div class="ff-empty__title">{{ _("No models are registered") }}</div>
        <p class="ff-empty__body">
          Register one with <code class="ff-mono">@admin.register(Model)</code>, then make
          sure the module is imported — see
          <code class="ff-mono">fort.autodiscover(...)</code> and
          <code class="ff-mono">fort.include_admin(...)</code>.
        </p>
      </div>
    </div>
  {% endif %}
{% endblock %}