Skip to content

Cross-link the case studies beyond the previous/next pager - #227

Merged
carsonSgit merged 1 commit into
mainfrom
feat/case-study-cross-links
Nov 7, 2026
Merged

carsonSgit merged 1 commit into
mainfrom
feat/case-study-cross-links

Conversation

@carsonSgit

Copy link
Copy Markdown
Owner

The only internal links between case studies were the previous/next pager — a single chain, where Argus pointed at Linky and CropCare no matter what the reader had just finished.

Each study now carries two deliberate cross-links, with a sentence explaining why they belong together, rendered as a Related work block above the pager.

Study Links to
TradeMind Argus, Linky
Botpress Fundica, Linky
Fundica Botpress, CropCare
Argus Linky, TradeMind
CropCare Argus, Botpress
Linky Argus, Botpress

Notes

  • getRelatedStudies(slug) in app/data/caseStudies.ts resolves each slug through getCaseStudyBySlug and drops unresolved entries — a renamed slug loses one link instead of throwing at build time.
  • Anchor text is the project title plus its type, so the links carry meaning for crawlers rather than "read more".
  • Styling reuses the existing card language (--rule, --hover-bg, 12px radius) and collapses to one column under 640px.

Verified

  • npx tsc --noEmit clean, npx biome ci . clean (43 files)
  • npm run build exit 0; all six exported pages contain exactly 2 related links
  • Rendered check in headless Chrome: two-card grid with type / title / reason, consistent with the pager below it

@vercel

vercel Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
carsonspriggs Ready Ready Preview Nov 7, 2026 7:49pm UTC

The only internal links between studies were the sequential pager, so the
internal link graph was a single chain: Argus only ever pointed at Linky and
CropCare regardless of what a reader had just finished reading.

Each study now carries two deliberate cross-links with a sentence explaining
the connection, rendered as a "Related work" block above the pager.

  trademind  -> argus, linky
  botpress   -> fundica, linky
  fundica    -> botpress, cropcare
  argus      -> linky, trademind
  cropcare   -> argus, botpress
  linky      -> argus, botpress

`getRelatedStudies` resolves slugs through `getCaseStudyBySlug` and drops
anything unresolved, so a renamed slug loses one link instead of throwing at
build time.
@carsonSgit
carsonSgit force-pushed the feat/case-study-cross-links branch from 58551cd to 1810d08 Compare November 7, 2026 19:49
@carsonSgit
carsonSgit merged commit a3a3386 into main Nov 7, 2026
4 checks passed

This branch was successfully deployed

1 active deployment
Preview — 1810d08f Deployed Nov 7, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant