-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FP-1022 a.k.a. Task/gh 191 support light navbar for dark logos #386
Conversation
Codecov Report
@@ Coverage Diff @@
## main #386 +/- ##
==========================================
+ Coverage 63.99% 64.81% +0.82%
==========================================
Files 398 205 -193
Lines 11970 5102 -6868
Branches 2060 1313 -747
==========================================
- Hits 7660 3307 -4353
+ Misses 3990 1672 -2318
+ Partials 320 123 -197
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR can be greatly simplified, after CMS makes theme-dependent CSS changes built-in.
Notice: To Do's on the CMS PR (TACC/Core-CMS#192) may render this PR moot, or much simpler. |
This PR is moot since TACC/Core-CMS#202 performs GH-191 without editing Doc nor Portal. |
Overview
For ProTX, support a light navbar for dark logo. See TACC/Core-CMS#192 for complete details.
Pull Requests
CMS Projects PR: Core: GH-191: Support new theme setting Core-CMS-Resources#41Portal PR: FP-1022 a.k.a. Task/gh 191 support light navbar for dark logos #386Docs PR: https://bitbucket.org/taccaci/frontera-tech-docs/pull-requests/16/task-gh-191-support-light-navbar-for-darkRelated Jira tickets:
Summary of Changes:
docs
image to one fortask/GH-191-…
branch. ← Should I do this?Testing Steps:
See TACC/Core-CMS#192.
UI Photos:
See TACC/Core-CMS#192 for all CMS & Docs & Portal screenshots.
Light Navbar For Dark Logo
Yes, I am using a light logo here. The navbar switch works. The logo is controlled by configuration already.
Notes:
Loading another script should not be a major performance issue, because we use http2 protocol, which "multi-tasks" asset downloads. If this is a performance issue, then I can use React to perform the same task (previous commits do so), but that will delay the header color swap, which is undesirable UX.