-
Notifications
You must be signed in to change notification settings - Fork 10
Nigels landing page #983
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
base: main
Are you sure you want to change the base?
Nigels landing page #983
Conversation
[diff-counting] Significant lines: 1208. This diff might be too big! Developer leads are invited to review the code. |
Visit the preview URL for this PR (updated for commit a96a738): https://cornelldti-courseplan-dev--pr983-nigels-landing-page-bkmk00fh.web.app (expires Fri, 16 May 2025 01:13:09 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 6d4e0437c4559ed895272bbd63991394f1e0e933 |
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.
Looks amazing Nigel! Can't wait to see the final landing page after the scaling bug is fixed :) Great job!!
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.
Yeah, to add to Nidhi's comments, to fix the scaling issues, I think good first steps would be:
- Instead of using the explicit pixel values (which don't scale well on mobile/different aspect ratio screen sizes), use CSS flexbox.
- Some of the transform properties, especially when combined with absolute pixel values, can contribute to the "text off the page" issue, depending on the device you use. I'm not too well-versed in this, but I think changing your approach to not use
transform
would be better. - Adding media queries to explicitly target mobile devices— the current ones only apply the CSS properties under them to devices with a breakpoint of "large" or under
I think we should definitely discuss this during the next CoursePlan standup/work sesh, this is a pretty complicated frontend design and getting the CSS just right for this is going to be difficult.
Look at closed pr #976