feat(enclave): standardize branding page to the redesigned shell (LC-469) #447
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/enclave-branding-redesign"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Standardizes the enclave Branding page (
/enclave/{id}/branding) to the redesigned enclave-settings shell. Refdata/ref-enclave-branding.png. It was the last enclave surface still on the old flat, full-width, un-carded style with a plain breadcrumb. Closes LC-469.Changes
.lc-set-cards, centered..lc-swatchnative color input + an editable hex field, two-way synced, with a live preview applying the chosen primary/accent to a header bar + button.?saved=1); validation errors render a styled banner; the Save button shows a "Saving..." working state..input/.btn; explanatory copy kept as muted.lc-set-help; light/dark via tokens.A self-contained
branding.js(gated on[data-lc-branding]) handles the swatch↔hex sync, preview, logo validation, and save toast, so the page does not depend on the enclave-settings redesign.Scope / safety
Template + JS + CSS + i18n only - no change to the branding handler, data model, validation limits, routes, or
hx-swap-oobtargets.Note on history
This branch was cut before #446 (LC-463, enclave settings) merged to main, so I merged current
origin/mainin (no force-push) to absorb it and resolved the append-point conflicts (base.html, main.css, en/es enclave.ftl) by keeping both sides. The PR diff is now branding-only (6 files).Verification
just build-css,just check(clippy + fmt clean),just test,just test-saasall green (branding 19/19, enclave-nav 10/10, coyote 7/7).just verifybuilt the release binary clean; itsserver-upharness lacks the mandatoryLETS_CHAT_BUNYIP_SSO_*startup vars, so the standalone server cannot boot to serve/loginin this sandbox (environmental, not a regression).🤖 Generated with Claude Code