-
Notifications
You must be signed in to change notification settings - Fork 2
GH-245/FP-1097: v1–v2 Migration Stylesheet (via submod) #274
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-245/FP-1097: v1–v2 Migration Stylesheet (via submod) #274
Conversation
Also, add comments about certain commented-out code.
Avoid this error that occurred on A2CPS ``` AttributeError: module 'taccsite_custom._shared' has no attribute 'default_app_config' ``` via Core-Portal-Deployments 91966f8.
|
A2CPS CSS Fixes (to match v1 UI more closely, and in an isolated manner) have been added. |
taoteg
left a comment
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.
LGTM!
|
The approve-er has has requested (private message) to confirm his approval before I merge. |
taoteg
left a comment
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.
LGTM!
Related
This PR relies on TACC/Core-CMS-Resources#59.
Overview
Add optional stylesheet to load v1 styles for CMS migrations that don't have a new design.
Issues
a.k.a. Fix CEPv1 Migration Style Discrepancies #245
a.k.a. https://github.com/TACC/Core-CMS-Resources/issues/56
Changes
Screenshots
Homepage
Paragraph Font Size
Testing
Environments
Changes
Dropdown font size should be:
16pxParagraph font size should be:
15pxmigrate.v1_v2.cssScreenshots
All style should match between:
on all pages (excluding content within iframes†).
Obvious failures would be…
Built Output
Test
.envasCUSTOM_ASSET_DIR=frontera-cmsand runnpm run build…Expect no errors. Expect the following CSS build file output:
Output
taccsite_custom/…/static/…/css/build/migrate.v1_v2.cssTest
.envas the following and runnpm run build…CUSTOM_ASSET_DIR=example-cmsCUSTOM_ASSET_DIR=a2cps-cmsCUSTOM_ASSET_DIR=neuronex-cmsExpect no errors. Expect the following CSS build file output:
taccsite_custom/…/static/…/css/build/migrate.v1_v2.cssNotes
To Do (Done)
taccsite_customconflict.Known Issues
Layout Change at Different Screen Widths than v1
Layout changes happen at slightly different screen widths, because Bootstrap 3 → Bootstrap 4 moves breakpoints by one notch.
Snippets
For Sites Migrated Before GH-245 (Frontera)
GH-245: CSS: Temp. Fix Migration Style Discrepancies
gh-245-css-temp-fix-migration-style-discrepanciesFor Sites Migrated During/After GH-245 (3Dem.org, etc.)
GH-245: CSS: Migration Stylesheet CoreV1 to CoreV2 (last commit: …)
gh-245-css-migration-stylesheet-corev1-corev2