Refactor duplicated code in Jekyll templates #97
+32
−37
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.
Overview
This PR refactors duplicated code found in the Jekyll templates to improve maintainability and follow DRY (Don't Repeat Yourself) principles. The changes eliminate 10 lines of duplicated code across layout files while maintaining identical functionality.
Changes
1. Layout Inheritance Refactoring
Problem:
_layouts/home.htmlduplicated the entire HTML structure from_layouts/default.html, including DOCTYPE declaration, html tags, head include, and body wrapper.Solution:
home.htmlto extenddefault.htmlusing Jekyll's layout inheritancedefault.htmlto conditionally apply thehomeclass to the body element when rendering pages with the home layoutpage.layout == 'home'for reliable detectionBefore (
_layouts/home.html):After (
_layouts/home.html):2. Date Formatting Extraction
Problem: Date formatting logic was duplicated between
_layouts/post.htmlandblog.html, with slightly different format strings.Solution:
_includes/date-format.htmlthat acceptsdate(required) andformat(optional) parametersBefore:
After:
{% include date-format.html date=page.date %} {% include date-format.html date=post.date format="%b %-d %Y" %}Impact
Testing
Changes follow standard Jekyll patterns and maintain backward compatibility. The site will render identically to before.
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.