> ## Documentation Index
> Fetch the complete documentation index at: https://help.folify.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a Developer Portfolio That Gets You Hired

> Learn which blocks, sections, and tips help developers build a Folify portfolio that impresses recruiters, proves technical ability, and wins jobs or contracts.

A developer portfolio needs to do one thing well — prove you can build things. This guide walks you through what to include, which Folify blocks to use, and how to make your portfolio stand out when applying for jobs or contracts.

## What to Include

These are the sections that make developer portfolios stand out to recruiters and hiring managers.

<CardGroup cols={2}>
  <Card title="Projects" icon="folder-open" href="/building/content-blocks">
    Link every project to a live demo or GitHub repo
  </Card>

  <Card title="Tech Stack" icon="code" href="/building/content-blocks">
    Languages, frameworks, and tools you use daily
  </Card>

  <Card title="Work Experience" icon="briefcase" href="/building/content-blocks">
    Roles, companies, and what you shipped
  </Card>

  <Card title="GitHub Activity" icon="github" href="/building/content-blocks">
    Contribution graph showing coding consistency
  </Card>
</CardGroup>

## Recommended Blocks

Add these Folify blocks to build a complete developer portfolio. Each block targets a specific piece of information recruiters look for.

<Accordion title="Header Block">
  Your first impression. Include your name, title (e.g. "Full-Stack Developer"), avatar, and a short bio that tells visitors who you are and what you build. Keep the bio to two or three sentences.
</Accordion>

<Accordion title="Skills Block">
  Display logos for the languages and frameworks you use most — React, TypeScript, Node.js, Python, and any others relevant to the roles you're targeting. Visual logos are faster to scan than plain text lists.
</Accordion>

<Accordion title="Projects Block">
  Showcase 3–5 of your best projects. For each one, include a project name, short description, the tech used, a link to the live demo, and a link to the source code on GitHub.
</Accordion>

<Accordion title="GitHub Streak Block">
  Display your GitHub contributions graph directly on your portfolio. A streak graph shows recruiters that you write code consistently — not just when a deadline is looming. Connect your GitHub account to pull in live contribution data.
</Accordion>

<Accordion title="Experience Block">
  Present your work history as a timeline. List each role with the company name, dates, and a brief summary of what you shipped or accomplished — not just your job title.
</Accordion>

<Accordion title="Contact Block">
  Give visitors a direct way to reach you — a contact form or a mailto link. Make it the last section so it's easy to find after someone has reviewed your work.
</Accordion>

## Tips for Developer Portfolios

<Steps>
  <Step title="Link every project to a live demo or GitHub repo">
    Screenshots alone aren't enough. Recruiters and engineers want to see working code. If a project is no longer live, link to the repository with a clear README that explains how to run it locally.
  </Step>

  <Step title="Show your tech stack with logos, not just text">
    Visual recognition is faster for recruiters who scan dozens of portfolios. Use the Skills Block to display technology logos in an organized grid rather than listing them as plain text in your bio.
  </Step>

  <Step title="Add a GitHub contributions graph">
    A contribution graph proves consistency and ongoing activity — it shows you write code outside of work, not just when you're on the clock. This signal carries real weight with technical hiring managers.
  </Step>
</Steps>

<Tip>
  Focus on 3–5 of your best projects rather than listing everything you've ever built. Quality beats quantity — a small set of well-documented projects with live demos is far more persuasive than a long list of unfinished side experiments.
</Tip>