Github Markdown Readme

Posted on  by admin
Article version:

Click on the image you'd like to display in Github (this brings up the 'Object Details' page) Copy pasta that URL (the one starting with https not gs) into a new browser tab/window; Copy pasta the new generated URL - it should be longer - from your new browser tab/window into your Github README file. So your Markdown files will have correct links both in Github and Github Pages. The index page of your website can be a file or a file. If both exists the file has priority. You should be able to use any Github Flavored Markdown. Known differences between Github and Github Pages. No automatic links with Github Pages. The GitHub profile-level README feature allows more content than the bio profile, supports markdown, which means you can play more visually with the content, and the README becomes considerably more accessible as it is positioned above pinned repositories and takes up as much space above the web page fold as you want.

Github Readme Markdown Image

Article version:

You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.

In this article


Github Markdown Readme

You can add a README file to a repository to communicate important information about your project. A README, along with a repository license, contribution guidelines, and a code of conduct, communicates expectations for your project and helps you manage contributions.

For more information about providing guidelines for your project, see 'Adding a code of conduct to your project' and 'Setting up your project for healthy contributions.'

A README is often the first item a visitor will see when visiting your repository. README files typically include information on:

  • What the project does
  • Why the project is useful
  • How users can get started with the project
  • Where users can get help with your project
  • Who maintains and contributes to the project

If you put your README file in your repository's root, docs, or hidden .github directory, GitHub will recognize and automatically surface your README to repository visitors.


If you add a README file to the root of a public repository with the same name as your username, that README will automatically appear on your profile page. You can edit your profile README with GitHub Flavored Markdown to create a personalized section on your profile. For more information, see 'Managing your profile README.'

Section links in README files and blob pages

Many projects use a table of contents at the start of a README to direct users to different sections of the file. You can link directly to a section in a rendered file by hovering over the section heading to expose the link:

Relative links and image paths in README files

You can define relative links and image paths in your rendered files to help readers navigate to other files in your repository.

Github Markdown Readme

A relative link is a link that is relative to the current file. For example, if you have a README file in root of your repository, and you have another file in docs/, the relative link to in your README might look like this:

GitHub will automatically transform your relative link or image path based on whatever branch you're currently on, so that the link or path always works. You can use all relative link operands, such as ./ and ../.

Relative links are easier for users who clone your repository. Absolute links may not work in clones of your repository - we recommend using relative links to refer to other files within your repository.

Further reading

  • 'Adding a file to a repository'
  • 18F's 'Making READMEs readable'