Sometimes you don't need a whole new profile — you need one section fixed. This page collects working Markdown examples for the sections developers most often get stuck on.
Headline example
# Hi, I'm Priya — Data Engineer building pipelines that don't page me at 3am
Specific and slightly personal beats generic. "Passionate about technology" tells a reader nothing; a role plus a concrete angle does.
Tech stack grid example
<p>
<img src="https://img.shields.io/badge/Python-3776AB?logo=python&logoColor=white" />
<img src="https://img.shields.io/badge/PostgreSQL-4169E1?logo=postgresql&logoColor=white" />
</p>
Keep this to one row. A grid that wraps to three or four rows stops reading as a stack summary and starts reading as clutter.
Project card example
### FileSync
Reduced sync latency by 40% for a 10k-user internal tool.
[Live Demo](#) · [Source](#)
Stats widget example
Swap yourname for your actual GitHub username — the most common reason this widget shows a broken image is a placeholder username left unchanged.
Frequently Asked Questions
Why does my stats widget show a broken image?
Almost always because the username parameter in the URL still says a placeholder value instead of your real GitHub username.
How many badges should I include in a tech stack row?
Six to ten is the practical ceiling before it starts reading as clutter rather than a quick summary.
Can I use these snippets in a project README, not just a profile README?
Yes, the project-card and code-block patterns work the same way in either context.