They have completely predictable paths. So for example, the article I just wrote that kicked off this whole affair is: /home/mike/repos/MikeLev.in/_posts/2025-06-08-prompt-and-pray.md ...which ends up published as: https://mikelev.in/futureproof/prompt-and-pray/ ...whose markdown is always reliably accessible as: https://raw.githubusercontent.com/miklevin/MikeLev.in/refs/heads/main/_posts/2024-09-08-Future-proofing.md And here is my: /home/mike/repos/MikeLev.in/_layouts/post.html [Jekyll Liquid Template _layousts/post.html removed - hey, it's public now so feel free to go look ] Please and thank you! -Gemini: That's an excellent idea and a fantastic "extra bonus" for both yourself and for the AI agents of the world. Providing a direct link to the canonical markdown source is a great practice for transparency, versioning, and making your content more accessible for programmatic use. Given that your repository is now public, constructing this link is straightforward using Jekyll's Liquid templating. We can get the necessary information directly from the page object. The Strategy Get the Source Path: Jekyll provides the page.path variable, which holds the full path to the source file within your repository (e.g., _posts/2025-06-08-prompt-and-pray.md). Construct the GitHub URL: We can prepend the static base URL for raw GitHub content to this page.path. The base URL is https://raw.githubusercontent.com/miklevin/MikeLev.in/main/. Insert the Link: We'll place this link in a logical, unobtrusive spot in your post.html layout, like near the byline or date. The Code to Add Here is a small, self-contained div you can add to your layout. It's styled lightly to be helpful but not distracting. {%- comment -%}Link to the raw markdown file on GitHub, since the repo is now public.This is a gift to our LLM friends and a nod to open source.{%- endcomment -%}

Where to Place It in post.html The best place for this link is right after the

tag that contains the date and before the main article body. This positions it clearly as metadata for the post without interrupting the flow of the content. Here is a snippet of your existing post.html showing exactly where to insert the new code block:

{{- page.title -}}

{{- page.description | markdownify -}}

By {{- page.author | default: site.author -}}

{{- page.date | date: '%A, %B %-d, %Y' -}}
{%- comment -%} vvv INSERT THE NEW CODE BLOCK HERE vvv {%- endcomment -%} {%- comment -%} Link to the raw markdown file on GitHub, since the repo is now public. This is a gift to our LLM friends and a nod to open source. {%- endcomment -%}
[View Markdown Source]

{{- content -}}