Introduction

If you're a developer or someone who works with developers, chances are you've seen the GitHub profiles of some of the most successful people in your field. Their profiles always seem to be well-written and engaging—but what is it about them that makes them so memorable?

GitHub profile README is a GitHub feature that debuted in July 2020. A README file is normally used to describe the repository for which it was created; we can utilize this feature to define our complete profile and what we do. It allows developers to show what they’re currently working on, their GitHub Stats, etc. This page is written in Markdown and is immediately shown when a profile on GitHub is opened. If used properly, it can even act as a basic resume where we highlight our key skills.

GitHub is a popular collaboration management platform used by many open source businesses so that developers from across the world can participate in project development. But a lot of programmers use GitHub as their portfolio, which implies it contains all of their prior work. Therefore, anybody looking to hire us as talent can readily view our projects. At that point, GitHub starts to double as a portfolio in addition to a source of collaboration and versioning tools. We must make our GitHub as aesthetically pleasing as we can.

Here are a few GitHub profiles with stunning profile READMEs:

For more inspiration, there are some amazingly innovative and unique profile READMEs listed in awesome-github-profile-readme!

A profile README aids the developer in emphasizing all the skills they want to and as we use markdown to make it, it’s extremely flexible and easy to make attractive. It gives us full control of how we want to present our profile. Consistently updating it is crucial as it gives those who visit our profile more clarity on what we’re currently working on and what we’ve already done. Your GitHub profile is an extension of your professional identity. It's where you showcase your skills and experience, so it's important that you do a good job representing yourself.

Your GitHub profile can be an extension of your professional identity.

Your GitHub profile is an extension of your professional identity. It's where you showcase your skills and experience, so it's important that you do a good job representing yourself.

How to make one:

It’s extremely simple to make one, let’s get into it step by step:

Create a new repository with the same name as your GitHub username. For example, the name of my profile README repository would be deepeshaburse since my username is deepeshaburse.
The next step is to set up the structure in markdown:

Use proper syntax and don't forget to use the proper file extension. Markdown files must be saved as .md files, not .mdx or any other extension (e.g., .txt). If you're using GitHub for Mac, use this tool to convert your README into a valid markdown document before submitting it for the review! You can also use an online service if you prefer not to have any special software installed on your machine at all times; just make sure that whatever method you choose has been tested and approved by someone else who knows what they're doing!

\
Next, we add content to the markdown file. Images, gifs, stats, etc. are often used to make the profile look more attractive. Images and gifs can easily be added using the HTML tag. There are a few HTML tags that we are allowed to use, this is one of them. Searching emoji names on https://emojipedia.org/emoji/ for appropriate emojis seemed to be the simplest method I could find. and then referencing https://www.fileformat.info/index.htm to look up its HTML element. These HTML entities can be used in markdown and should be rendered properly by your browser.
The text should be in bullets so it is clearer to understand and focuses on all the main points.

Add your own flair to it

Readme Stats

Your GitHub profile should ideally highlight all your current activities and contributions. To showcase these, we use GitHub Stats. You can create GitHub stats for your contributions and repositories using GitHub Readme Stats, which you can then attach to your README. You will get different “cards” for stats for different purposes like the stats for the topmost language you’ve used on GitHub, details on the number of contributions, commits, and so on. It also allows us to customize the colors, themes, icons, etc. You can also add your personal blogs if you write them.

As for graphs, you should avoid using them unless you are proficient in using them. Using too many stats or graphs too can make your profile look messy and crowded, so use only what is needed and showcases your strengths.

Readme Badges

Developers are often seen using badges to display the different skills and technologies they know or prefer. It is recommended to segregate these based on different factors, say you segregate based on languages, different cloud platforms, or different tools you are familiar with. To nicely visualize these, you could use shields.io.

Readme Profile Picture and Illustrations

You can also add an image & illustration of yourself to your README. This is a great way to personalize it and make it look more like you. If you don't have any photos of yourself, consider taking some before adding them! If you already have some links on your profile page such as Twitter or LinkedIn, then feel free to include them here too! You'll want to include links that are relevant for people who are viewing this page in search results when they go looking for someone with a similar skill set (s).

Social Links

In order to be more easily accessible to recruiters and other developers, one should add their social media handles. Use icon links to make it easy for visitors to find/notice whatever you decide to include.

To include these in markdown, you can use the following markdown:

## 📫 𝙷𝚘𝚠 𝚝𝚘 𝚛𝚎𝚊𝚌𝚑 𝚖𝚎:
𝚈𝚘𝚞 𝚌𝚊𝚗 𝚛𝚎𝚊𝚌𝚑 𝚖𝚎 𝚊𝚝 𝚝𝚑𝚎 𝚎𝚖𝚊𝚒𝚕 𝚒𝚗 𝚖𝚢 𝚐𝚒𝚝𝚑𝚞𝚋 𝚙𝚛𝚘𝚏𝚒𝚕𝚎. 𝙵𝚘𝚕𝚕𝚘𝚠 𝚖𝚢 𝚜𝚘𝚌𝚒𝚊𝚕𝚜!



[](https://linkedin.com/in/)
[](https://twitter.com/)
[](https://instagram.com/)

\

Latest Blog posts and publications

If you have a blog or other online publication that people can read, link it up (and make sure it's an active one).
Link all of your blog posts together in one place under “Blogs” or something similar; they should be named accordingly so they can be easily searched using Google Search (for example., My Blog). You may also want to add links back into the main text where applicable so readers who come across this page, later on, don't miss anything important!
```
## Latest Blog Posts 
- [Learn Readme from absolute scratch](https://dev.to)
- [Learn Javascript from absolute scratch](https://dev.to)
- [Learn Technical writing from absolute scratch (https://dev.to)
```

Conclusion

Writing a well-formatted README file is an engaging way to stand out from the crowd and get your GitHub profile noticed—and it takes very little time. If you follow these steps, you’ll have a beautifully formatted README ready in no time. I hope this blog gave you a basic idea of how to make a GitHub profile README—it's recommended that you keep it original and try to showcase your personality through it!

Step-by-step guide for crafting a stunning GitHub profile README