/Ultimate-Readme-Template

Are you struggeling sometimes with your Readme? This Template shows you step by step which elements you can add for a clean and informative README file...

GitHub commit activity GitHub contributors GitHub forks GitHub last commit GitHub code size in bytes

Add your Title here ✅

=> Choose a self-explaining name for your project and add a little description

=> Use "Windows" + "." to add emojis to your title 👌😊

=> The third symbol from right on top (with a magnifier symbol) in VSC shows you the preview

=> If you want to know more about design Elements of a README: MARKDOWN CHEAT SHEET



Style Elements ✅🎨

=> Colour up your text with THIS

=> Use different fonts such as THIS

=> More than TWO SPACE CHARACTERS will create a:

word wrap!

=> Use these brakes to generate SPACING: <br />


Installation ✅

=> Use external sites to refer on informations you got from other web pages such as this example here.

example guides (if you integrate it into a bash, others can copy this statement)

=> Listing some specific steps to guarantee a perfect guidance.

$ git clone https://example.com
$ cd ../path/to/the/file
$ npm install
$ npm start

=> If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.



Code and Syntax highlighting ✅

=> Blocks of code are fenced by lines with three back-ticks. Either you fence a word to highlight it, you fence a whole block of words or you go all in: Fence the desired part and add the suitable language to highlight it the best way as possible:

var s = "JavaScript syntax highlighting";
alert(s);
s = "Python syntax highlighting"
print s
import dogbar

dogbar.pluralize('shiba') # returns 'shibas'
dogbar.singularize('akitas') # returns 'akita'
No language indicated, so no syntax highlighting. 
But let's throw in a <b>tag</b>.

=> You can also use raw HTML in your Markdown, and it'll mostly work pretty well.

Definition list
Is something people use sometimes.
Markdown in HTML
Does *not* work **very** well. Use HTML tags.


Contributing

=> Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Therefore we can talk about an "issue template", but hopefully that's not necessary. * Smiles *



License

MIT 🟢✔



Table of Contents

=> A typical "Inhaltsverzeichnis"

  1. General Info and Visuals
  2. Technologies
  3. Installation
  4. Collaboration
  5. FAQs


General Info and Visuals ✅

=> Write down the general informations of your project. Furthermore you are always welcome to add screenshots, videos or other visual elements for a better understanding:

This is a cute Shiba! Hug him!



Technologies ✅

=> Add a list of technologies used within the project:



Collaboration ✅

=> Give instructions on how to collaborate with your project.

A perfect opportunity is to use quotes like these.

Or another one if you wish.



FAQs ✅

=> A list of frequently asked questions

  1. This is a question in bold: Answer of the first question with: italic words.
  2. Second question in bold: To answer this question we use an unordered list:
  • First point
  • Second Point
  • Third point
  1. Third question in bold: Answer of the third question with: italic words.
  2. Fourth question in bold
Headline 1 in the tablehead Headline 2 in the tablehead Headline 3 in the tablehead
text-align left text-align center text-align right