Files
LLeMbas/src/lembas/web/templates/admin/group_detail.html
T
HomerandClaude Opus 5 a16510aba8 The interface speaks Slovak
969 strings, an instance default and a per-person choice, and no half-done corner:
the admin prose is translated too. Design and reasoning: LLeMbas.wiki/Translations.

KEYED BY THE ENGLISH SENTENCE

A missing entry renders the key, which is the English -- so an untranslated string
looks as it always did, an English instance is byte-for-byte 1.6.0, and a
half-finished catalogue is a half-translated page rather than a page of dotted key
names. The cost is that editing an English sentence orphans its translation
silently, which is what tests/test_translations.py asserts in both directions.

No gettext: .po -> .mo is a build step and this project does not have one.

A JINJA GLOBAL, AND THEREFORE A CONTEXTVAR

`t()` is a global for the reason `brand` already documents -- render() is bypassed
by 25 TemplateResponse calls and 8 get_template().render() calls, the latter being
the SSE frames, which have no Request at all. A global is bound once at import and
the language is per person, so the active language is a ContextVar set per request.

🚨 `get_current_user` had to become `async def`. FastAPI runs a sync dependency in a
threadpool, and anyio copies the context in and discards it on the way out -- so
the language was set where nothing could see it and every page rendered in the
instance's language whatever anybody had chosen, with no error anywhere.

NOT TRANSLATED, ON PURPOSE

Everything a model reads: the 60 prompt fragments, and the dates in harness.py,
schedule/runner.py and schedule/compile.py. Only `i18n.stamp` is localised, and
only where a person reads it -- with the *format* translatable as well as the
words, because "26. septembra 2026" is a different pattern rather than the same one
with different words in it. A process locale is not an option: global, not
thread-safe, two people's pages at once.

A second fragment telling models to answer in the reader's language was written
during this work and removed: `core.style` has said it since long before, and
test_an_empty_override_turns_a_fragment_off caught the duplicate.

THE BULK PASS

1213 sites wrapped by a one-off script that only touched patterns it could not
misread. It got three wrong in a way that mattered -- `t('…')` inside `attr="…"`
where the sentence held an apostrophe, closing the Jinja string and 500ing two
pages whose partials no test renders. tests/test_translations.py now compiles all
110 templates. It also wrapped the product's own name, an SSH key header, a
keystroke hint and an example URL, all taken back out: a string is not
translatable just because it is a string.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-26 14:46:33 +00:00

131 lines
5.5 KiB
HTML

{% extends "admin/_layout.html" %}
{% from "_macros.html" import icon, model_avatar %}
{% set section = "groups" %}
{% block title %}{{ group.name }} - Groups - {{ brand.name }}{% endblock %}
{% block heading %}{{ group.name }}{% endblock %}
{% block admin_content %}
<p class="admin-lede">
<a href="/admin/groups">{{ icon("chevron-left", "icon--sm") }} All groups</a>
· A group only ever <em>{{ t("adds") }}</em>. Anything already in the baseline is shown
below as such, so a tick here that changes nothing looks like one.
</p>
{% if saved %}
<div class="alert alert--success">{{ icon("check", "icon--sm") }} <span>{{ saved }}</span></div>
{% endif %}
<form method="post" action="/admin/groups/{{ group.id }}" class="form-grid">
<section class="card">
<h2 class="card__title">{{ t("Name") }}</h2>
<div class="field">
<label class="field__label" for="name">{{ t("Name") }}</label>
<input class="input" id="name" name="name" value="{{ group.name }}" required>
</div>
<div class="field">
<label class="field__label" for="description">{{ t("What it is for") }}</label>
<input class="input" id="description" name="description"
value="{{ group.description }}" maxlength="1000">
</div>
</section>
<section class="card">
<h2 class="card__title">{{ t("Permissions this group adds") }}</h2>
{% for section_name, defs in permission_groups.items() %}
<div class="field">
<span class="field__label">{{ section_name }}</span>
{% for definition in defs %}
<label class="checkbox perm-row">
<input type="checkbox" name="permission" value="{{ definition.key }}"
{{ 'checked' if (group.permissions_json or {}).get(definition.key) }}>
<span>
<strong>{{ definition.label }}</strong>
{% if baseline[definition.key] %}
<span class="badge">{{ t("already in the baseline") }}</span>
{% endif %}
<span class="perm-row__desc">{{ definition.description }}</span>
</span>
</label>
{% endfor %}
</div>
{% endfor %}
</section>
{#
Quotas. Every one is zero-for-no-limit, and an *empty* box is different from
a zero: empty is "this group has no opinion" and contributes nothing to the
resolution, zero is "unlimited" and wins outright. Saying that here is the
only place somebody will read it.
#}
<section class="card">
<h2 class="card__title">{{ t("Quotas") }}</h2>
<p class="card__lede">
Resolved across a person's groups by <strong>{{ t("maximum") }}</strong> — the union
rule applied to numbers, so a second group can only grant more.
<strong>{{ t("Leave a box empty") }}</strong> for “no opinion”, and use
<strong>0</strong> for “no limit”, which beats any number another group
sets. Administrators are unlimited whatever is here.
</p>
<div class="field-row">
{% for key, label, description in limit_defs %}
<div class="field">
<label class="field__label" for="limit-{{ key }}">{{ label }}</label>
<input class="input" id="limit-{{ key }}" name="limit_{{ key }}"
type="number" min="0" step="1"
value="{{ limits.get(key, '') }}" placeholder="{{ t('no opinion') }}">
<p class="field__hint">{{ description }}</p>
</div>
{% endfor %}
</div>
</section>
{#
Membership lives here and only here. It used to be on the user page as well,
and a full-form POST from either side overwrote what the other had shown.
#}
<section class="card">
<h2 class="card__title">{{ t("Members") }}</h2>
<p class="card__lede">{{ t("The one place membership is edited. A user's own page links here rather than offering a second control for the same value.") }}</p>
<div class="checkbox-row">
{% for person in users %}
<label class="checkbox">
<input type="checkbox" name="user_ids" value="{{ person.id }}"
{{ 'checked' if person in group.users }}>
<span>{{ person.name }} <span class="faint text-xs">{{ person.email }}</span></span>
</label>
{% endfor %}
</div>
</section>
<section class="card">
<h2 class="card__title">{{ t("Models this group unlocks") }}</h2>
<p class="card__lede">{{ t("A model marked public is available to everyone; one that is not is available to the groups named here. Model access is separate from permissions — one says what somebody may do, the other what with.") }}</p>
<div class="checkbox-row">
{% for model in models %}
<label class="checkbox">
<input type="checkbox" name="model_ids" value="{{ model.id }}"
{{ 'checked' if model in group.models }}>
<span>{{ model_avatar(model, "model-avatar model-avatar--sm") }} {{ model.label }}</span>
</label>
{% endfor %}
</div>
</section>
<div class="btn-row">
<button class="btn btn--primary" type="submit">{{ t("Save group") }}</button>
</div>
</form>
<section class="card">
<h2 class="card__title">{{ t("Remove") }}</h2>
<form method="post" action="/admin/groups/{{ group.id }}/delete"
data-confirm="Delete {{ group.name }}? Its members keep their accounts.">
<button class="btn btn--danger btn--sm" type="submit">
{{ icon("trash", "icon--sm") }} Delete this group
</button>
</form>
<p class="field__hint">{{ t("Members keep their accounts and lose whatever this group granted them. Every share naming this group goes too — nothing cascades to those, so they are deleted explicitly.") }}</p>
</section>
{% endblock %}