Write clean, formatted documents using plain text.
Markdown is a simple way to format text using ordinary characters.
You'll find it everywhere in tech—especially in README files, GitHub, documentation, notes, and project wikis.
1. Headings
Use #:
# Heading 1
## Heading 2
### Heading 3
#### Heading 4
The more # characters, the smaller the heading.
2. Bold & Italic
Bold:
**important**
Italic:
*emphasis*
Both:
***very important***
3. Paragraphs
Just write normally:
This is a paragraph.
This is another paragraph.
Leave a blank line between paragraphs.
4. Lists
Bullet list
- Apple
- Banana
- Orange
You can also use:
* Apple
* Banana
* Orange
Numbered list
1. Install Git
2. Clone the project
3. Make changes
4. Push changes
5. Links
[Google](https://google.com)
The text inside [] is what users see.
6. Images

Example:

The description helps when the image cannot be displayed.
7. Code
Inline code
Use backticks:
Run `git status` to check your changes.
Result:
Run git status to check your changes.
Code block
Use three backticks:
```bash
git status
git add .
git commit -m "Update README"
```
You can specify the language:
bash
javascript
python
java
sql
json
This enables syntax highlighting on platforms that support it.
8. Blockquotes
Use >:
> Keep it simple.
Result:
Keep it simple.
Useful for highlighting notes, quotes, or important information.
9. Horizontal Line
Use three hyphens:
---
Creates a divider.
10. Tables
| Name | Role |
|---|---|
| Jacob | Developer |
| Mary | Designer |
| John | Tester |
Result:
| Name | Role |
|---|---|
| Jacob | Developer |
| Mary | Designer |
| John | Tester |
11. Task Lists
Useful for project checklists:
- [x] Create repository
- [x] Add README
- [ ] Add documentation
- [ ] Deploy application
Result:
- Create repository
- Add README
- Add documentation
- Deploy application
12. Escaping Characters
Sometimes you want Markdown characters to appear as normal text.
Use \:
\*This is not italic\*
Result:
This is not italic
13. Emojis
Many Markdown platforms support emojis:
🚀 Deployment complete
✅ Tests passed
⚠️ Warning
Some also support:
:rocket:
:white_check_mark:
Support varies by platform.
14. HTML
Many Markdown implementations allow HTML:
<strong>This is bold</strong>
But don't rely on HTML unless you need it.
Plain Markdown is usually easier to read and maintain.
15. A Simple README
A basic README.md might look like this:
# My Project
A simple application that manages users.
## Features
- User registration
- Login
- User management
## Installation
```bash
git clone https://github.com/example/my-project.git
cd my-project
```
## Usage
```bash
npm install
npm start
```
## Technologies
- Node.js
- MySQL
- Docker
## License
MIT
That's already enough for a useful project README.
The Essentials to Remember
| What you want | Markdown |
|---|---|
| Heading | # Heading |
| Bold | **text** |
| Italic | *text* |
| Bullet | - item |
| Numbered list | 1. item |
| Link | [text](url) |
| Image |  |
| Inline code | `code` |
| Code block | ``` |
| Quote | > quote |
| Divider | --- |
| Table | | column | |
| Checkbox | - [ ] task |
The Golden Rule
Markdown is meant to stay readable even before it's rendered.
This:
# My Project
This is a **simple** project.
## Installation
```bash
npm install
- Easy to install
- Easy to use
- Open source
is still perfectly understandable as plain text.
That's the beauty of Markdown.
---
### Remember
You don't need to memorize Markdown.
Just remember these:
```text
# Heading
** ** Bold
* * Italic
- List
[]() Link
` ` Inline code
``` Code block
> Quote
| | Table
If you can read it, you can write it.
