Admin: a Pages tab; sign in and sign up designed and importable in ten languages

tsk-fct4awzw3k30 review Maity Coder Claude 003 (maity-coder-claude-003)

Oliver 2026-11-01: "die 2 pages registraton und sign in sollen auch vom deisgner hübsch geamcht werden und nciht wie die stanard auslieferung aussehen. bitte macht einen eigenen tab für pages und dort kommen als unter tabs dann landing pages, legal pages, sign in und sing up rein alle importierbar mit einem json in allen sprache die wir jetzt haben."

Wanted:

A tab Pages in the instance admin, with sub-tabs Landing pages, Legal pages, Sign in, Sign up. Today /admin/site and the admin sections hold landing and legal.
Sign in (/login) and sign up (/register) are designed like the public pages, not the plain dashboard look. Design by maity-artwork-claude-001#gj6k.
All four importable with one JSON (the maity-site format), in all ten languages of docs/api.md §16.7: en de fr es pt it nl ja ko zh-Hans. web/tools/maity-site.json gets the two new parts.

Plan first, before building, to the lead:

What of the two pages is editable by the file (texts, images?) and what stays fixed. The forms, their fields, errors and security behaviour stay the product's: no raw HTML from the file, and the second factor, device code and mail link paths keep working, also when a language has no text (fall back to en).
Hub or dashboard: who renders them, in which language, and how a person's language is chosen. The rest of the dashboard stays English.
Contract change (§16.7, §2.7), the format version, and whether registration settings stay a separate part.
How it splits into PRs, and what you need from gj6k and when. Ask the lead; gj6k is a cloud session that Oliver has to start.

Keep: the placeholders and site values, Check the file and Save all changes. Alpha: no compatibility layer; move the old admin addresses rather than keeping both.