-
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
feat(core-styles): v2 #569
Conversation
The previously installed branch was merged to main.
- fix(fonts): fp-1891 add regular italic, also add black (#71) - feat(objects): warning about still-disabled o-site - feat(components): icon updates from Core-Portal - docs(trumps): comment about lifespan of u-empty - chore(elements): body margin 0 - feat(dist): commit dist for clients relying on it (#70) - chore: import dependencies in each pattern
In Core-Styles, icon CSS moved: trumps/icon → components cortal.icon.
J.R. and I agree a real CDN makes sense for Core-Styles, long-term. J.R. doesn't know about this temp solution yet. He'll have better idea.
No need to re-build Core-Styles since we have it's `dist/`. Related PR: TACC/Core-Styles#70
- Add core styles version setting. - Load core-styles from pseudo-CDN. - Use new CSS layer tech to load stylesheets.
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.
Round 1 Review Comments
######################## | ||
# TACC: CORE STYLES | ||
######################## | ||
|
||
# Only use integer numbers (not "v1", not "0.11.0"), | ||
# so templates can load based on simple comparisons | ||
TACC_CORE_STYLES_VERSION = 0 | ||
|
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.
added TACC_CORE_STYLES_VERSION
setting
(so each cms can decide when it is ready to use newer 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.
Eventually, will we be able to drop the if blocks for the version check, once all the portals are migrated forward? Or do you want to keep this setting to future-proof v3 development.
If retained, is the v1/v2 filename nomenclature the presence of the site.
prefix in the v1 filenames (eg. 'site_cms/css/build/site.app.blog.css' vs 'site_cms/css/build/app.blog.css')?
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.
Uncertain, the future of this setting is.
I want to remove it after migration, but we may be slow to migrate. Proof: CMD still has CMS v1 (pre Core-Styles) CSS like A2CPS and Frontera.
Yes, the site.
prefix distinguishes CMS styles that use Core-Styles v0.
I do not like this, because it is not obvious. I think these site.____.css
stylesheets belong in https://github.com/TACC/Core-CMS/tree/main/taccsite_cms/static/site_cms/css/src/_migrations. But Core-Portal and Frontera Tech Docs expect the filenames site.header.css
and site.tacc-search-bar.css
, and I have been too lazy to work in those repos again.
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.
Round 2 Review Comments
taccsite_cms/contrib/taccsite_system_specs/templates/system_specs.html
Outdated
Show resolved
Hide resolved
taccsite_cms/static/site_cms/css/src/_core-styles/core-styles.base.css
Outdated
Show resolved
Hide resolved
taccsite_cms/static/site_cms/css/src/_imports/components/c-button.css
Outdated
Show resolved
Hide resolved
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.
Had a few inquiries and minor comments, but LGTM!
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.
Peer Review Feedback
- Move
site.___.css
into_migrations
.
feat(core-styles): v2 - move v3.10 stylesheets to _migration #656 - (after merge) Ask CMD whether the conversion of a CMS-side can be tasked to an intern.
I asked CMD privately; H.P. answers affrimatively. - (after merge) Provide an architectural illustration.
I will do this better, later, to more people. I can reference Shared UI - CSS - Architecture. - (after merge) Determine how to make the CSS less daunting.
This is a constant effort. After feat(core-styles): v2 - move v3.10 stylesheets to _migration #656, this PR will represent an improvement.
I moved the |
@tacc/core-styles v2+ does not limit input field length. But APCD relies on it (the limit was built for APCD's first form.) This commit need not be in main until APCD loads Core-CMS post #569. TACC/Core-CMS#569
Overview
site.___.css
.Related
Changes
Core CMS
TACC_CORE_STYLES_VERSION
setting(so each cms can decide when it is ready to use newer core-styles)
(not using https://unpkg.com cuz I worry that depending on an external service for primary stylesheets)
site.___.css
stylesheets to be minified versions of what they were in v3.10.1TACC_CORE_STYLES_VERSION
TACC_CORE_STYLES_VERSION
Core Styles
Testing & UI
Future Compatibility
dev/tup-cms
branch*: feat(tup-cms): accent colors & new ui patterns & ui demo fixes tup-ui#67(this used an older commit of
task/get-core-styles-beyond-0.11.0
)Backwards Compatibility