-
Notifications
You must be signed in to change notification settings - Fork 1
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
GH-101/FP-1458: Header Redesign #222
Draft
wesleyboar
wants to merge
142
commits into
main
Choose a base branch
from
task/GH-101-header-redesign
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains 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
- Migrate `branding_logos` CSS to `c-branding` & `c-logo`. - In `s-header` style `.c-logo` not `.navbar-brand`. - Update and format markup for `header_branding` and `header_logo`. - Comment on now-unused secrets values.
…design--branding-bar
…ng-bar GH-101: Branding Bar
This was
linked to
issues
May 13, 2021
- Remove now-moot taccsite_custom:frontera-cms search bar font sizes. - Support CSS custom selectors (known external bug). - Test CSS custom selectors (known external bug). - Remove outdated comment from `c-branding`. - Set `c-logo` image height in component stylesheet. - Add TODO for `html { font-size: 62.5%; }` - Add arrow "mixin" (note: using `%-arrow` syntax). - Redesign header (but not dropdowns and not portal nav). - Remove now-moot `s-portal-nav` styles. - Add & Update header env variables for themes. - Perform "GH-129: Do Not Support CMS Menu Nav Link & Dropdown".
Prevent dropdown link from being flagged as active.
- (Real Fix) Ensure colors are available to Docs. - (Possible Fix) Ensure correct colors are available to Portal.\* \* The Portal has its own settings/color.css that is almost identical.
- Load new styles solely for docs header. - Force branding styles on old markup. - Migrate subsite selectors from `trumps/s-header` to `tools/selectors`. - Rename `:--in-__subsite__` selectors to `:--from-__subsite__`. - Create new styles solely for docs header. - Document "For (Other Sites)" i.e. `trumps/for-docs.*.css` stylesheets.
Unset Docs' `img { max-width; }`. Docs does this too but for old markup.
- Install `merge-lite` for deep merge constants and theme data. - Use env() vars for header height. - Remove unnecessary code and improve comments. - Create constants for theme JSON. - Merge constants on top of theme data. - Update theme data comment syntax.
- Add frontera-cms logo width overwrite (temp. ineffectual, see GH-223). - Prevent Core (but not a project) from stretching logo too wide. - Align CMS nav for narrow logos. Allow project-specific adaptation.
- Remove redundant color assignment for nav-link.
…riables Task/gh 101 header redesign env variables (update)
- Add font weight constants. - Add border constants. - Style dropdowns and use new constants.
Use correct global var not wrong env var for branding bar bkgd.
Scope dropdown styles to header so as to not effect any other dropdowns.
1. Scope header-specific `.c-branding` styles with `.s-header`. 2. Clarify which `s-header` is being styled and why. 3. Remove `s-header` ID from sample header markup. 4. Add `s-header` class to `header-branding`. 5. Replace `s-header` ID with `header-navbar` ID.
Portal needs to overwrite Bootstrap's color for active `dropdown-item`.
Instead of defining a value to be overwritten, set a fallback. This reduces one level of overwrite when tracking/debugging values.
Ensure Portal & Docs line-height (in header) matches CMS.
- The responsive space between nav items now considers portal elements. - Whether header is loaded on portal is noted by presence of a class.
…design--navigation-bar
This was
linked to
issues
May 18, 2021
wesleyboar
added
priority ▲
High priority
and removed
priority ▲▲
Very high priority
labels
Aug 5, 2021
Merged
…ask/GH-101-header-redesign
Base automatically changed from
task/GH-191-support-light-navbar-for-dark-logos
to
main
September 23, 2021 01:12
wesleyboar
added
priority ━
Medium priority
and removed
priority ▲
High priority
labels
Sep 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To Do
✓ Before Small-Screen UI Design
✓ After Small-Screen UI Design
→ After Small-Screen UI Design Review
→ Clean Up Code
gh-101
class and usage→ Merge in Sub-Branches
task/GH-101-header-redesign
task/GH-101-header-redesign--mobile-nav-layout-2
… Clean Up PR Desc
Overview
Redesign the header.
Related
Note to Self
This difference is almost made up for by #264. Progress has been delayed by other work.
Changes
env()
variables.all pull requests
complete changelog
:not()
with multiple selectors (fff0a3d)env()
vars for all themes (ea43ec9)merge-lite
(ea43ec9)env()
support replaces themc-branding
c-logo
backdrop-filter
(dc4f7db)@custom-media
for navigation breakpoints (59a97d3)x-arrow
x-hide
x-mobile-button
s-portal-nav
sample markup (to reflect future Portal markup)u-hide
[data-status="loaded"]
after Portal nav load (for styling) (e38594d)Screenshots
Hover over an image to see a description (on desktop browser).
Wide Screen (1200px)
(No State)
CMS Nav: Link (Hover) | Dropdown (Open) | Dropdown Item/Link (Hover)
Portal Nav: Closed | Link (Hover) | Open
Portal Nav: Closed | Link (Hover)
Narrow Screen (768px)
(No State)
Nav Open: Close Button (Hover) | CMS Link (Hover)
Dropdown Open: CMS Link (Hover) | CMS Dropdown Item/Link (Hover)
Dropdown Open: Login Link (Hover) | Search Field (Focus) | Search Field (Input)
Dropdown Open
Nav Open
Nav Open: Link (Hover) | Dropdown (Open) & Link (Hover) | Dropdown (Open) & Dropdown Item/Link (Hover)
Nav Open: Dropdown (Open)
Minimum Width (320px)
CMS
CMS does respect cross-site minimum width.
Nav Open
Nav Open
Nav Open: Portal Nav
Docs
Docs does not yet respect cross-site minimum width.
Docs can respect cross-site min width. I have temporary solution for now.
Nav Open
Nav Open
Portal
Portal does not respect cross-site minimum width.
Portal can not easily respect cross-site min width until a mobile design.
Nav Open
Testing
Set up testing environment using method from Test CMS Changes. Specifically,
npm run settings
(new step, from GH-191: Theme (for ProTX Light Header & TACC Blue Header) #192)npm ci
|install
npm run build
Test these elements are present, functional, and match design on the matching subsites:
Table
Subsite ↓
Legend:
Test these elements have these layouts occur at the matching breakpoints on the matching subsites:
Table
Elements ↓
Ensure dropdown icon is:
List
⌄
when dropdown is open^
when dropdown is closedNotes
Known Issues
On mobile nav, the dropdown toggle ("chevron") is not thick enough.
I am forgoing adding complexity in code to solve this, because there should be a Cortal icon for this shape.
Stand-alone CMS navbar collapses for a wider screen than before.
A CMS that belongs to a Portal is not affected, because it already behaves like this.
Known Deviations From Design
Expected to Remain
Some color(s) of Search Bar use a standard color instead of color in design.
I have prior private permission to make these "fixes" during translation. I plan (eventually) to teach Portal devs how to do the same.
Mobile Portal Nav Menu
If the mobile portal nav menu were moved to outside the navbar dropdown, then these likely would all be resolved. But Design has agreed to let me do that later.
On narrow screen, Search Bar height and Search Bar + Portal Nav link height are shorter than design.
I just didn't want to maintain another value when the two were so close—and sometimes Design is close when they mean to match. If this is noticed as a bug, then I will fix it.
On medium and wide screen, space left of Logo and right of Portal Nav do not match design.
So, I ignored 30px and made spaces align because my experience shows me that aligning and consistency is Design's goal here, not an exact pixel value.
On narrow screen, Portal Nav dropdown is pushing down CMS Nav.
This is a stopgap to not have the Portal Nav dropdown fall over CMS Nav, but not yet move it to the Designer-suggested location (which is a deviation form design, see Known Deviation 6).
On narrow screen, Portal Nav link is wider than necessary (for short usernames)
m
's).On narrow screen, Portal Nav location is not deviating from design as Designer suggested it should.