loading...
Cover image for Making GitHub Portfolio

Making GitHub Portfolio

uyadav207 profile image Utkarsh Yadav ・1 min read

New Features are awesome and some of them are for good. GitHub brought you some secret features that are no more a secret. and is spreading like a πŸ”₯.

Let's not waste time and strike is down...

Making your README Platter

Prerequisite : Markdown writing skills

Step 1 : Making a repository.

  • + sign is where you have to hit.
  • select new repository.

Alt Text

Step 2: Naming Conventions.

Name the Repository same as your GitHub Username. No other way allowed.

Then a special message pops out see below.

Alt Text

Make the Repository Public as to show the changes and Readme Platter to whoever visit your profile.

Step 3: Give a Nice touch..

This is what's on your part to play with. I am done here.

If you wants any of the suggestions. or do not know what to write.

You can consider my repository as an example.

Profile

Hey there! πŸ‘‹ I’m Utkarsh Yadav, A student, developer with a background in Computer Science and has keen interest in web and mobile technologies using the JavaScript ecosystem. I am also very much involved in writing technical Blogs and loves to write about the stuff related Js ecosystem etc. on DEV Community

🎯 Find me Interesting?

Open source Teams/Organizations I'm in.

Work

  • πŸ“Œ Repository : 49

  • πŸ“Œ Pull Requests : 15

  • πŸ“Œ Major Contributions : ISTMNCR | GitHub | TeamTanay

  • πŸ“Œ I can help you in : Web Applications | Android | IOS | Mordern PWAs Website

  • πŸ“Œ Tech Stack : ReactJS | GatsbyJS | ReactNative | NodeJS | ExpresJS

Follow me on :

Twitter | dev.to | Instagram | Telegram





DO COMMENT IN COMMENT SECTION AND FOLLOW ME AND MY WORK ON GitHub

Posted on by:

uyadav207 profile

Utkarsh Yadav

@uyadav207

THE PROFITABLE PROGRAMMER | MERN Developer πŸ‘¨β€πŸ’» | Self Taught | coding | Passionate | Learning Enthusiast | Optimistic | Smart-worker.

Discussion

markdown guide
 

I haven't tried this yet, but one of the early screenshots I saw from GitHub showed that you can use your .github repo, instead of a <username> repo, and that will also work.