Files
LLeMbas/src/lembas/web/templates/admin/workflow_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

128 lines
5.5 KiB
HTML

{% extends "admin/_layout.html" %}
{% from "_macros.html" import icon %}
{% set section = "images" %}
{% block title %}{{ workflow.name or "New workflow" }} - {{ brand.name }}{% endblock %}
{% block heading %}{{ workflow.name or "New workflow" }}{% endblock %}
{% block admin_content %}
<nav class="crumbs">
<a class="crumbs__back" href="/admin/images">
{{ icon("chevron-right", "icon--sm crumbs__icon") }} Image generation
</a>
</nav>
{% if error %}
<div class="alert alert--error">{{ icon("warning", "icon--sm") }} <span>{{ error }}</span></div>
{% endif %}
<form method="post"
action="{{ '/admin/images/workflows' if is_new else '/admin/images/workflows/' ~ workflow.id }}"
class="form-grid">
<section class="card">
<h2 class="card__title">{{ t("What it is") }}</h2>
<div class="field">
<label class="field__label" for="name">{{ t("Name") }}</label>
<input class="input" id="name" name="name" required maxlength="120"
value="{{ workflow.name }}" placeholder="{{ t('SDXL, photographic') }}">
<p class="field__hint">{{ t("Shown to you, in the list.") }}</p>
</div>
<div class="field">
<label class="field__label" for="slug">{{ t("Name the model uses") }}</label>
<input class="input input--mono" id="slug" name="slug" required maxlength="48"
value="{{ workflow.slug }}" placeholder="{{ t('sdxl-photo') }}">
<p class="field__hint">{{ t("Lowercase letters, digits, hyphens and underscores. This is what the model writes when it picks this workflow.") }}</p>
</div>
<div class="field">
<label class="field__label" for="description">{{ t("Description") }}</label>
<textarea class="textarea" id="description" name="description" rows="3"
placeholder="{{ t('Photographic and slow. Best for people, interiors and product shots at 1024px.') }}">{{ workflow.description }}</textarea>
<p class="field__hint">
The only thing the model has to choose with, so say what this is
<em>{{ t("for") }}</em> rather than what it contains. It never sees the graph.
</p>
</div>
<div class="field">
<label class="checkbox">
<input type="checkbox" name="enabled" value="true" {{ 'checked' if workflow.enabled }}>
<span>{{ t("Offer this workflow") }}</span>
</label>
</div>
</section>
<section class="card">
<h2 class="card__title">{{ t("The workflow") }}</h2>
<div class="field">
<label class="field__label" for="workflow">{{ t("ComfyUI API format") }}</label>
<textarea class="textarea input--mono" id="workflow" name="workflow" rows="20"
spellcheck="false">{{ workflow_text }}</textarea>
<p class="field__hint">
Export this from ComfyUI with <strong>{{ t("Export (API)") }}</strong>, not Save — the
two formats are different and only the API one can be submitted.
</p>
<p class="field__hint">
Then put a placeholder where each value goes. A placeholder that is the
<em>{{ t("whole") }}</em> value keeps its type, so
<code>"steps": {{ '{{steps}}' }}</code> sends the number 20 rather than the
text “20”; one inside a longer string is substituted as text, so
<code>"{{ '{{prompt}}' }}, masterpiece"</code> works. Anything you leave out
takes its default.
</p>
</div>
</section>
<section class="card">
<h2 class="card__title">{{ t("The placeholders") }}</h2>
<p class="card__lede">
Every hole a template may carry, what it fills, and what it resolves to
right now. <code>{{ '{{prompt}}' }}</code> is required — without it every
image would be the same one, whatever anybody typed.
</p>
{# The current value beside each name, the way /admin/prompts shows a
variable's. A legend that lists names and not values answers "what may I
write" and not "what will happen", and the second is the question
somebody has while looking at a workflow that came out wrong. #}
<div class="ref-list">
{% for name, kind, what, current in placeholder_help %}
<div class="ref-row">
<code>{{ '{{' ~ name ~ '}}' }}</code>
<span>
{{ what }}
{% if name == "prompt" %}<strong>{{ t("Required.") }}</strong>{% endif %}
</span>
<code class="faint">{{ current }}</code>
</div>
{% endfor %}
</div>
<p class="field__hint">
Two of these are not spelled the way ComfyUI spells them, which is the
mistake that costs an afternoon: <code>{{ '{{model}}' }}</code> fills
<code>ckpt_name</code> and <code>{{ '{{sampler}}' }}</code> fills
<code>sampler_name</code>.
</p>
<p class="field__hint">
The right-hand column is what an omitted placeholder resolves to today —
the instance defaults from the image settings page, falling back to the
built-in floor. A model may override any of them except
<code>{{ '{{batch}}' }}</code>, which is yours alone.
</p>
</section>
<div class="btn-row">
<button class="btn btn--primary" type="submit">
{{ "Add workflow" if is_new else "Save changes" }}
</button>
<a class="btn btn--ghost" href="/admin/images">Back</a>
{% if not is_new %}
<button class="btn btn--danger" type="submit" formnovalidate
formaction="/admin/images/workflows/{{ workflow.id }}/delete"
data-confirm-button="Delete the workflow “{{ workflow.name }}”? Chats that used it fall back to the default.">{{ t("Delete") }}</button>
{% endif %}
</div>
</form>
{% endblock %}