DIY guide · Medium API
Your portfolio should reflect what you actually publish
Hiring managers and clients Google you—and compare your personal site to your Medium profile. When they do not match, you look inactive or sloppy. Automate the bridge once; look current forever.
Medium is distribution. Your site is the proof.
Medium is excellent for reach. It is mediocre for showing the breadth of your work the way you want: ordered, categorized, beside your projects and contact form. Developers and creators still want a domain they own—especially when fundraising, consulting, or applying for senior roles.
The failure mode is familiar: you ship twelve essays on Medium and your portfolio shows three case studies from 2022. Not because you are lazy—because syncing manually does not survive real life.
What "synced portfolio" means
It does not mean duplicating every typo forever. It means your site's Writing or Blog section lists the same canon you care about on Medium, with accurate titles, links, and optionally full text for readers who never leave your domain.
Static site generators make this especially pleasant: Markdown files in git, preview in CI, deploy on push. The Medium API becomes just another input—like RSS used to be, except it still works in 2026.
The automation pattern
Reliable automation resolves your public handle to a stable user id, lists articles on a schedule, and for each new id fetches Markdown (or HTML) into the path your generator expects. Front matter stores article_id so rebuilds are idempotent.
Run it nightly or on every deploy. Nightly is enough for most portfolios; deploy-time is perfect when you only want posts that passed your Medium publish button.
Why teams use Zenndra here
Portfolio sync is read-heavy and embarrassingly public when it breaks. You want an API with clear errors, documented fields, and formats that map to content collections—not a scraper that returns HTML soup.
Zenndra's user and article endpoints are built exactly for "list my work" and "give me the body" workflows. No headless browser. No cookie jars.
Stack notes (without religion)
Hugo, Astro, Eleventy, and Next all work: the output is files or MDX. Designers often keep Medium as canonical URL in front matter while rendering on-site for experience. Pick one strategy and stay consistent for SEO.
Beyond the minimum
Once the basics work, add reading time and hero images from article metadata. Group posts by tag. Feature three "best of" on the homepage. The API gives you more than titles—use it when you are ready to look premium.
The bar to call it done
You are done when you published on Medium Tuesday and your site shows it Wednesday without you remembering. That is the whole product.