Skip to content
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

Closed

Conversation

wesleyboar
Copy link
Member

@wesleyboar wesleyboar commented Apr 16, 2021

Overview

For ProTX, support a light navbar for dark logo. See TACC/Core-CMS#192 for complete details.

Note: Testing requires:

  • new CMS branch task/GH-191-… (recent image: taccwma/protx-cms:a86a5e5)
  • new Docs branch task/GH-191-… (recent image: taccwma/frontera-docs:aea2e4f)

Pull Requests

Related Jira tickets:

Summary of Changes:

  • New: Add new required CMS setting.
  • New: Change docs image to one for task/GH-191-… branch. ← Should I do this?
  • New: Add new script to load CMS theme.

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
Light Navbar - Portal

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.

@codecov
Copy link

codecov bot commented Apr 16, 2021

Codecov Report

Merging #386 (0de4a6f) into main (5155fed) will increase coverage by 0.82%.
The diff coverage is n/a.

❗ Current head 0de4a6f differs from pull request most recent head d2ec48f. Consider uploading reports for the commit d2ec48f to get more accurate results
Impacted file tree graph

@@            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     
Flag Coverage Δ
javascript 64.81% <ø> (ø)
unittests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
server/portal/utils/exceptions.py
server/portal/libs/agave/models/metadata.py
server/portal/settings/unit_test_settings.py
server/portal/apps/auth/urls.py
...erver/portal/apps/googledrive_integration/tasks.py
server/portal/apps/tickets/views.py
server/portal/libs/googledrive/operations.py
server/portal/apps/accounts/apps.py
...er/portal/apps/licenses/migrations/0001_initial.py
server/portal/libs/agave/operations.py
... and 183 more

@wesleyboar wesleyboar changed the title Task/gh 191 support light navbar for dark logos FP-1022 a.k.a. Task/gh 191 support light navbar for dark logos Apr 16, 2021
Copy link
Member Author

@wesleyboar wesleyboar left a 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.

server/portal/templates/base.html Show resolved Hide resolved
@wesleyboar wesleyboar marked this pull request as draft April 16, 2021 19:09
@wesleyboar
Copy link
Member Author

Notice: To Do's on the CMS PR (TACC/Core-CMS#192) may render this PR moot, or much simpler.

@wesleyboar
Copy link
Member Author

This PR is moot since TACC/Core-CMS#202 performs GH-191 without editing Doc nor Portal.

@wesleyboar wesleyboar closed this Apr 21, 2021
@wesleyboar wesleyboar deleted the task/GH-191-support-light-navbar-for-dark-logos branch April 21, 2021 19:09
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.

1 participant