Fix layout breaking issues with Jekyll structure and proper asset paths #3
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.
Fixes layout breaking issues on the GitHub Pages site by implementing proper Jekyll structure and correcting asset path handling. The site was experiencing layout instability due to missing DOCTYPE, improper asset references, and lack of CSS reset rules.
Issues Fixed
1. Asset Path Problems
index.htmlwas referencing"styles.css"but the actual file was"style.css"2. Layout Instability
Changes Made
Jekyll Structure Implementation
_layouts/default.htmlwith proper HTML5 structure, viewport meta tag, and responsive design_config.ymlwith correctbaseurl: ""for user/organization sitesindex.htmlto use Jekyll front matter and layout system{{ '/path' | relative_url }}filter for proper GitHub Pages compatibilityCSS Improvements
assets/css/main.cssfollowing Jekyll conventionsbox-sizing: border-boxto prevent layout shiftsEnhanced Functionality
assets/js/main.jswith smooth scrolling navigation and section animations<main role="main">and accessibility improvementsTechnical Details
The site now works correctly for both:
username.github.io) withbaseurl: ""username.github.io/repo-name) when baseurl is configuredBefore:
After:
This ensures assets load correctly regardless of the GitHub Pages deployment context.
Testing
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.