feat(apollo-vertex): add customize appearance pattern (store + form + utilities)#596
Draft
creilly11235 wants to merge 1 commit intomainfrom
Draft
feat(apollo-vertex): add customize appearance pattern (store + form + utilities)#596creilly11235 wants to merge 1 commit intomainfrom
creilly11235 wants to merge 1 commit intomainfrom
Conversation
… utilities) Ports the CustomizeAppearance page from vertical-medical-mrs into a reusable Apollo Vertex pattern: a tenant-admin settings form for company name, logo, and brand colors. This slice is the grab-and-go core — the form composition, state store, color math, and theme enforcer. Preview and docs follow in a stacked PR. - CustomizeAppearance.tsx uses only @uipath/* registry primitives (Button, Card, Collapsible, Input, Label, PageHeader, Spinner, Sonner). Layout uses Tailwind v4 container queries so the form responds to its rendered container width — sidebar-collapsed shells, iframes, and narrow panels all lay out correctly. Cards reveal color pickers via the registry Collapsible with a parallel fade. - branding-store.ts exposes useSyncExternalStore + a pluggable BrandingAdapter with load / save / uploadLogo / clearLogo hooks. Default adapter persists to localStorage. Logo uploads are staged locally and only pushed to the adapter on Save, so backends that separate settings records from file attachments (e.g. Data Fabric) don't upload on every preview. - color-utils.ts provides oklch <-> hex conversion and generates a full primary-shade ramp plus sidebar vars from a single primary color. - use-branding-theme-enforcer.ts locks the app to light mode when a custom theme is active (primary ramp is light-calibrated) and restores the user's previous theme on switch-back. Call from the app root inside ThemeProvider.
creilly11235
requested review from
0xr3ngar and
alincadariu
and removed request for
a team
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
10 tasks
Dependency License Review
License distribution
Excluded packages
|
Collaborator
|
@petervachon this one needs integration with the platform, as this PR currently stores it in local storage. so if user A changes company logo, it won't be visible to others (only to him). switched it to draft for now cc: @0xr3ngar |
Collaborator
|
Totally makes sense. When it comes to storage and relying on the platform, what is the best way to flag requests like this? I imagine our team may use local or session storage to work through the UX, but will need to work in the hooks later on. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a pattern for allowing users to customize the appearance of their apps by updating the company name, logo, and primary and accent colors (custom colors lock the user into light mode only).