-
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
feat: update Core-CMS & Core-Styles, rename CMS Settings, Portal Purple to Blue #476
Conversation
157d165
to
81cb021
Compare
because latest image is not used
Core Styles v3 does not distinguish Portal colors. So, Portal need not worry about overrides.
Not necessary since Core-Styles 45dc5aa1.
It is deprecated.
Differences form Core-CMS resolved in Core-CMS commit 9efb52ff.
* chore: cmd-79/tv3-181 FAVICON → PORTAL_FAVICON * refactor: cmd-79/tv3-181 LOGO → PORTAL_LOGO * refactor: cmd-79/tv3-181 TACC_ → PORTAL_ * feat: cmd-79/tv3-181 Core-CMS image placeholder * test: cmd-79/tv3-181 new Core-CMS image * fix: correct branch translation to core-cms image * fix!: cmd-79 core-cms backwards-compatibility bugs With this update, there is an unexpected and bewildering UI change: - the navbar at 992px is collapsed - it should only collapse at 991px - this behavior is different than when using Core-CMS v4.8.3 * style: cmd-79 remove newline to simplify diff * fix: cmd-79 nav overflows header at certain screen widths * refactor: rename old Core-CMS settings to new * docs: PORTAL_NAV_WIDTH moved to correct section
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.
Notes for reviewers.
custom-selectors: true | ||
relative-color-syntax: true |
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.
custom-selectors
: moved / no-op
relative-color-syntax
: to change a color programmatically
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.
Renaming & updating CMS settings. Mostly no-op, cuz setting names are backwards-compatible.
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.
Not necessary since I now do this (much more simply) in Core-Styles.
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.
Not necessary since I updated the Core-CMS template of the same name.
color: var(--global-color-accent--secondary); | ||
color: var(--global-color-secondary--normal); |
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.
Uses Core-Styles v2 color var name instead of v1’s.
background-color: var(--global-color-accent--weak); | ||
background-color: var(--global-color-accent--xx-light); |
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.
Uses Core-Styles v2 color var name instead of v1’s.
background-color: var(--global-color-accent--weak); | ||
background-color: var(--global-color-accent--xx-light); |
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.
Uses Core-Styles v2 color var name instead of v1’s.
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.
Uses Core-Styles v2 color var name instead of v1’s.
color: var(--global-color-accent--secondary); | ||
color: var(--global-color-secondary--normal); |
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.
Uses Core-Styles v2 color var name instead of v1’s.
"postcss": "^8.4.38", | ||
"postcss-preset-env": "^10.0.2", | ||
"postcss-replace": "^2.0.1", |
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.
Updated to match Core-Styles’ versions.
- raw markup template (though tup-cms does not enable it) - muted container section (enabled by default)
Overview
Use latest Core-Styles and Core-CMS and PostCSS.
Note
More is added than removed because of
package-lock.json
.Important
After deploy to production, delete snippet #154.
Related
Changes
Testing & UI
Tip
Deployed to dev via v1.1.11-202409-02.
🐞 Fixes of Obscure Origin
Verify Instagram icon fills the 25x25 icon box.
See news article header changes that are good or acceptable.
Known Changes:
🆕 Portal Accent Color is Blue
Core-CMS v4.15 & Core-Styles v2.32
⚙️ Portal Message Style is Unchanged
Core-CMS v4.15 +4.16.1 & Core-Styles v2.32 +2.33.1
I had changed to CMS-style messages, but Designer (M.S.) and I agreed to revert.
⚙️ Colors Come From Design Tokens
Core-CMS v4.15—16 & Core-Styles v2.32—33
❗️Delete or Disable snippet "CSS: Button Color in Dark Contexts".
Verify color changes:
light blue is a little darker e.g.
light blue of active nav has similar contrast with text as light purple had
Verify no other color changes, especially in Footer.
Verify no console error about
:--dark-context-safe
.⚙️ Replaces Article Drop-Cap Class Snippet with Core Code
Core-CMS v4.14.1
div.s-drop-cap p
works automatically on articles with image that has captionp.s-drop-cap
works manually on articles with image with no caption⚙️ No Change Since ElasticSearch Setting Refactor
Core-CMS v4.14.0
Site deploys. Search works.
🐞 2nd-Level Breadcrumb Looks Disabled
Core-CMS v4.13.1 & Core-CMS v4.12.0
🐞 🆕 We Can Create Containers Again & Use Containers to Create Sections
Core-CMS v4.17.1 & Core-CMS v4.13.0 & Core-CMS v4.15.2
Before, creating a container resulted in a 500 error. Now, creating one works and you can make it double as a Section.
section.via.container.mov
9beb9ac
)⚙️ No Change Since Custom Email Code (Not Used by TUP Yet)
Core-CMS v4.13.0
⚙️ Replaces Existing Accessibility Fixes with Core Code
Core-CMS v4.13.0
Verify social media logos have the same accessibility attributes as before.
Use
aria-label
notaria-description
.⚙️ Rename Many Settings
Core-CMS v4.13.0 & Core-CMS v4.12.0 & Core-CMS v4.7.0
Verify header branding has not changed.
Verify logo markup has not changed besides removal of unused image class
tup
.Verify favicon and its markup have not changed.
Verify news list layout has not changed.
Verify news article header layout has mostly not changed.
See "Changes of Unknown Origin" for known changes.
⚙️ Other Releases are No-Op
Core-CMS v4.11.1 & Core-CMS v4.11.0
The changes in these releases do not affect TACC site.