Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / ucode static checks (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 24.10) (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 25.12) (push) Blocked by required conditions
- Russian translation. The admin pages, the LuCI menu and the router's messages (errors, Health checks, update steps, the service log) come in Russian with the new luci-i18n-dawnline-ru package, released beside the app. LuCI shows it when its language is Russian, or "auto" with a Russian browser - The translation installs with install.sh when LuCI is in Russian (or with --lang ru), follows every Dawnline update and rollback, and can be added or removed in Components → Dawnline → Translation - The portal speaks the visitor's language: it opens in the system's language and switches between English and Russian in place, from the language pill beside its QR code. It carries its own translation and needs no package - Set-up steps quote the apps' own menus word for word, in Russian too: AmneziaVPN is "+ → Insert → Continue" (it has no "Add server"), and the Mac and Windows menus of WireGuard and AmneziaWG have their real names - Questions in the portal (Reconnect, Remove) read from the left edge and close with Cancel, without × - Numbers, sizes and dates follow the page's language. A server that can't start says why in one sentence; event details and service log lines read as whole sentences - README in Russian (README_ru.md). rules/i18n.md: how strings are written and translated; CI checks the catalogs (npm run i18n:check)
4.1 KiB
4.1 KiB
UI design (Dawnline admin, portal and other panels)
The bar is a modern product UI (Linear / Vercel / Raycast level), not a "native" LuCI form. A plain label + input row, a bare radio list, three columns of check marks or a text dump is a first draft, never the result.
Approach
- Mock first. Any visible change beyond a one-line fix: show a mockup (2–4 genuinely different options when the direction is open) with a recommendation, then build the chosen one. Do not start coding a layout the user has not seen.
- Think past the obvious. When an option is rejected as "not it", propose new concepts, not variations of the same layout.
- Structure over text. Tiles, segmented controls, pills, round icon buttons, inline status, folded "Advanced" sections. Summaries first ("All 6 checks passed"), details on demand.
- No duplication. One place per fact (usage, device count, links). Remove what is repeated elsewhere on the page.
- Reuse the house patterns before inventing new ones:
dl-paramsfolded details with a rotating chevron,dl-tile2tiles, round icon buttons with tooltips,⋯menus (destructive and Pause inside, Pause in warn colour, "Delete" without an ellipsis), bottom toasts instead of LuCI banners, the same tiles on server and person pages. - Alignment and spacing are part of the design. Shared margins and edges, equal heights in a row, controls pinned consistently (top, not centred, when the user says so), nothing clipped or overflowing, single-line labels where they fit.
- No ellipsis on buttons or menu items ("Remove", not "Remove…"), even when they open a dialog. "…" only for progress ("Loading…") and truncated values.
- Colour means something: ok = green, warn/pause = orange, danger = red, accent = blue. Icons for states instead of words where obvious.
- Honest warnings belong in the UI (e.g. plain HTTP, Cloudflare throttling), shown where the choice is made.
Mocks look like the real product
A mock is judged against the page it will live on, so it must already look like it. Hand-drawn look-alikes with invented styles get rejected ("выбивается из дизайна").
- Study the existing pages first (the section being changed and its neighbours) and build only from their components:
dl-setseccards withdl-setsec-foot,dl-setrowrows with adl-need-icicon tile anddl-switch,dl-seg(sm,wide),dl-chip/dl-chipbtn,dl-list+dl-row,dl-table,dl-checks(the Health check list),dl-tile2tiles,dl-panel. A new class only when nothing fits, and then in the same tokens (--dl-*). - Buttons are
cbi-button: actions like Edit, Change, Rescan areneutralpills (as "Edit in Settings", "+ Add device"); Save and Install arepositive. No blue text links for actions. - Show only what changes. Do not add existing, unrelated controls (e.g. Devices or Access ends tiles) to a mock; say in the caption that the rest of the page stays.
- Build it from the real code and CSS, not from a copy:
- theme:
scp root@outline.lan:/www/luci-static/outline/{main.css,geist-*.woff2}into the mock folder, strip/luci-static/outline/from the font URLs,<html data-darkmode="true">; - Dawnline CSS: the files in
web/src/admin/styles/*.cssconcatenated in the order ofstyles/index.tsintodl.css; - markup: a small
mock.tsthat imports the realadmin/e,shared/icons,admin/ui/*andadmin/widgets/*(stub the LuCI globalswindow.E,dom.content,L.url), bundled withweb/node_modules/.bin/esbuild --bundle --format=iife.
- theme:
- Keep mocks outside the product repo, serve them with
python3 -m http.serverstarted from Bash (the preview server cannot read~/Documentson macOS), open them in the built-in browser, and delete the folder when the feature ships.
Done means seen
Deploy, then look at it in the browser (desktop width, and narrow when layout changes) before reporting. Check modals and drawers stack correctly and long values do not overflow. Look at it in Russian too: a visible change is localized in the same change (i18n.md), and Russian text is longer.