Repository navigation
Fix Jekyll rendering issue: remove .nojekyll and configure baseurl - #2
Draft
gravity-wh with Copilot wants to merge 3 commits into
Draft
gravity-wh with Copilot wants to merge 3 commits into
gravity-wh with Copilot wants to merge 3 commits into
Conversation
… matter Co-authored-by: gravity-wh <114725356+gravity-wh@users.noreply.github.com>
Co-authored-by: gravity-wh <114725356+gravity-wh@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Jekyll rendering issue on blog homepage
Fix Jekyll rendering issue: remove .nojekyll and configure baseurl
Oct 10, 2025
This branch was successfully deployed
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.
Problem
The site at https://gravity-wh.github.io/My-Blog/ was displaying raw front matter text instead of rendering the Jekyll theme properly. Users saw:
Instead of the expected blog homepage with posts and theme styling.
Root Cause
The issue was caused by three problems:
.nojekyllfile present - This file explicitly tells GitHub Pages to skip Jekyll processing and serve raw files directlyindex.htmlcontained a comment within the YAML front matter that could cause parsing issues/My-Blog) butbaseurlwas empty, causing asset paths to failChanges
1. Removed
.nojekyllfileThis file prevents Jekyll from processing the site. Since the repository uses Jekyll with the Chirpy theme and has a proper
_config.yml, this file should not exist.2. Fixed
index.htmlfront matterBefore:
After:
Comments within YAML front matter should be avoided to prevent parsing issues.
3. Configured baseurl
Before:
baseurl: ""After:
baseurl: "/My-Blog"Since this is a project site (not a user/organization site), the baseurl must match the repository name for proper asset loading and navigation.
4. Updated
.gitignoreAdded
.nojekyllto prevent accidental re-addition.Testing
bundle exec jekyll build/My-Blog/prefixResult
After these changes are deployed, the site will properly render with the Chirpy theme, display blog posts on the homepage, and all assets will load correctly.
Original prompt
💡 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.