Repository navigation
docs(readme): link the companion blog post - #15
Merged
Merged
Conversation
Point README.md at the live companion write-up so a visitor who lands on the repo can reach the story behind the tool: why the server exists, how the grounding round-trip and citation extraction work in the code, and how the default model was chosen on the evidence. Add the link in two natural spots: a short intro line after the opening description (for a first-time visitor arriving from social) and a full entry in the Learn more section, replacing the reserved slug placeholder now that the post is published.
cwest
commented
Jul 28, 2026
Owner
Author
There was a problem hiding this comment.
No changes needed.
The link lands in the two spots a reader actually wants it: the intro line right after the opening description, and the Learn more entry where it retires the reserved slug placeholder now that the post is published. Both point at the live URL, and the link text matches the page's own title. The framing describes what the post gives the reader rather than selling it.
Checked the rest against ground truth: README.md only (+9/-3), the repo:managed marker on line 1 is intact, the link resolves 301 to the trailing-slash URL then 200 with real content, no UTM on the caseywest.com link, and both CI jobs are green. The slug placeholder is gone.
Ready to merge.
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.
Point
README.mdat the live companion write-up so a visitor who lands on therepo can reach the story behind the tool: why the server exists, how the grounding
round-trip and citation extraction work in the code, and how the default model was
chosen on the evidence.
The link lands in two natural spots:
arriving from a link gets the "why does this exist" story immediately;
placeholder now that the post is published.
The link ships bare (no query parameters), matching the README's existing inline
markdown link style and sentence-case prose.
Verification
grep -n "building-gemini-search-mcp-grounding" README.mdreturns two hits.SERIES-SLUG-PLACEHOLDERremains in the README.curl -sILon the link resolves301 → /(trailing slash) →200.README.mdpasses (markdownlint-cli2, trailingwhitespace, EOF, mixed line ending, secret scan).
Post: https://caseywest.com/building-gemini-search-mcp-grounding-citations-and-choosing-a-gemini-model