Building a compelling DevRel portfolio is the fastest way to prove you can translate technical depth into community value. This guide shows how to combine Hashnode for writing, GitHub Actions for automation, and Netlify for instant static hosting into a single, recruiter‑ready showcase.
Why a Dedicated DevRel Portfolio Matters
Recruiters for developer advocacy roles look for evidence of technical writing, public speaking, and community engagement in one place. A curated portfolio signals that you understand the full advocacy loop: create, distribute, measure, iterate.
When hiring managers review candidates, they often scan for a live URL that demonstrates consistent publishing cadence and measurable impact. A static site that updates automatically removes the friction of manual uploads and keeps the content fresh.
Step‑by‑Step Architecture
Follow this repeatable pipeline to publish articles, demos, and talk recordings without manual FTP or copy‑paste.
- Set up a Hashnode blog – create a free account, map a custom domain (e.g.,
devrel.yourname.dev), and enable the Markdown editor. - Initialize a GitHub repository – store all Markdown files, assets, and a
netlify.tomlconfig. - Add a GitHub Actions workflow – on every push to
main, runhashnode-cli publish(or use the Hashnode API) and then trigger a Netlify deploy. - Configure Netlify – connect the repo, set the build command to
npm run build(orhugoif you prefer a static generator), and publish thepublicfolder. - Automate content sync – use a scheduled Action to pull Hashnode posts via RSS into the repo, keeping the site always current.
Choosing Content Pillars for Maximum Impact
Structure the site around three pillars that map directly to hiring criteria.
- Technical tutorials – deep‑dive guides on the product you want to advocate for.
- Community stories – case studies of meetups, hackathons, or open‑source contributions you organized.
- Speaking assets – slide decks, video embeds, and speaker‑note PDFs from conferences or webinars.
Each pillar should contain at least three polished pieces before you start outreach. This depth proves you can sustain a content program over time.
Optimizing Each Artifact for Search and Shareability
Every article should target a long‑tail keyword such as “how to debug WebAssembly with Chrome DevTools”. Add front‑matter fields for title, description, tags, and canonical_url so Netlify can generate proper meta tags automatically.
Leverage Open Graph and Twitter Card metadata to ensure clean previews when you share links on LinkedIn, X, or Dev.to. Consistent branding across platforms reinforces personal authority.
Measuring Portfolio Performance
Insert a lightweight analytics snippet (Plausible or Netlify Analytics) and track three metrics: unique visitors, time‑on‑page for tutorials, and conversion clicks to your LinkedIn or email. Review monthly and iterate the content calendar.
Set up a simple dashboard in Google Data Studio or Notion to visualize trends. Data‑driven adjustments demonstrate a growth mindset to prospective employers.
Common Pitfalls and How to Avoid Them
- Over‑engineering the stack – start with Hashnode + Netlify; add a static generator only when you need custom components.
- Neglecting mobile preview – Netlify’s deploy preview URLs let you test on device before merging.
- Forgetting to update the
sitemap.xml– the GitHub Action can runnetlify-cli sitemapon each deploy.
Conclusion
A focused DevRel portfolio built on Hashnode, GitHub Actions, and Netlify demonstrates both technical fluency and advocacy mindset. Publish one high‑quality piece per week, automate the deploy pipeline, and showcase measurable community impact to land your first advocacy role.