Skip to content

BAH-4635 | [Feature UI] White-Label Override Config Mechanism #252#116

Open
hamsavarthiniR-Bahmni wants to merge 7 commits into
masterfrom
BAH-4635
Open

BAH-4635 | [Feature UI] White-Label Override Config Mechanism #252#116
hamsavarthiniR-Bahmni wants to merge 7 commits into
masterfrom
BAH-4635

Conversation

@hamsavarthiniR-Bahmni

Copy link
Copy Markdown

No description provided.

"primary-active": "#004144",
"link-hover": "#005d5d",
"link-visited": "#8A3FFC",
"link-visited-on-dark": "#BE95FF",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

background variable sounds like a main background color of the application. Should we rename it ?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we rename it to background-secondary ? layer-01 is not self-explainatory key

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed earlier, we wanted to follow a white-labelling for branding related config name.
Theming is a feature for switching between white theme, dark theme or as CDS provides we can enable 4 variants of theme. But that is not yet build for bahmni. Here we are just overring default bahmni colors with implementer's brand colors (under white-labelling)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed, this white-label-extension.json is for new app... So should we follow the same folder structure as of other configs. openmrs/apps/home/v2/white-label-extension.json

- Rename bahmni-theme.json → bahmni-brand.json to reflect
  white-labelling/branding purpose rather than theme-switching
- Rename 'background' key → 'layer-01' to use the precise Carbon
  token name and avoid ambiguity with the app's main background

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
hamsavarthiniR-Bahmni and others added 4 commits May 15, 2026 17:18
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
- Rename brand-extension.json → white-label-extension.json
- Rename key layer-01 → background-secondary
- Rename key link-visited-on-dark → link-visited-inverse

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants