Improve mobile responsiveness and layout consistency#20
Merged
Conversation
This file contains hidden or 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
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.
Description
This Pull Request addresses the issue regarding mobile responsiveness and layout consistency across all project pages. It introduces a refined global typography hierarchy, fixes major header overflow bugs on mobile, resolves CSS class collisions on the Hub page, and ensures responsive forms and containers on all screens.
Fixes / Resolved Issues
bodyand.containerFlexbox collisions inviews/navbar.ejs(Hub page) that were breaking the global header and footer placement.Detailed Key Changes
1. Global Styles & Responsiveness (
public/styles.css).main-headertoposition: stickyand removed the hardcodedpadding-top: 80pxfrombody. The layout now flows dynamically and prevents content overlapping.heighttoautoand added flexible wrapping on navigation items at(max-width: 768px)so links scale elegantly on smaller screens.h1throughh6) and created a reusable.gradient-textstyle class for primary page titles.2. Page-Specific Layout Alignments (
views/)views/index.ejs): Added the missing<div class="welcome-section">wrapper container, resolving a bug where the landing page title and intro paragraph did not receive the beautiful gradient styling.views/about.ejs): Simplified page code by migrating local heading styles to use the new global.gradient-texthelper class.views/portfolio.ejs): Added the.gradient-textclass to the portfolio title for visual branding consistency across pages.views/contact.ejs): Wrapped the page components in.contact-containeras originally intended by the styles, limiting the form width on desktop screens to a readable600pxand making the form inputs and buttons fully responsive on mobile viewports.views/navbar.ejs): Removed destructive overrides onbody,*, and.containertags. Introduced scoped card classes (.hub-cardand.nav-grid) to allow the page to inherit global header/footer formatting while retaining its distinct card layout.How This Was Tested