Basic Formatting

NeedType ThisLooks Like
Bold**important**important
Italic*note*note
Bold italic***very important***very important
Strikethrough~~old~~old
Inline code`code`code

Headings

# Main Title
## Section
### Subsection

Lists

- Bullet item
- Another item
 
1. First step
2. Second step
3. Third step

Checkboxes

- [ ] Task not done
- [x] Task done

Tasks 101

- [ ] Normal task
- [x] Done task
- [ ] Task with due date 📅 2026-07-05
- [ ] Task with scheduled date ⏳ 2026-07-01
- [ ] High priority task 🔼

Tables

| Name | Status | Notes |
|------|--------|-------|
| API docs | Active | Update weekly |
| Vault guide | Active | Keep short |
[[Vault Guide]]
[[Obsidian Markdown 101|custom link text]]
[Website](https://example.com)

Attachments And Images

!image.png
!file.pdf

Tags

#work
#obsidian
#project-note

Highlight And Divider

Highlight: wrap text with two equals signs on both sides.
 

Quotes And Callouts

> Normal quote
 
> [!note]
> 
> Short note or reminder.
 
> [!warning]
> 
> Something to be careful about.

Code Blocks

```js
console.log("hello");
```

Common Habits

  • Use wikilinks for notes inside this vault.
  • Use normal Markdown links for websites.
  • Keep tables small; long tables are harder to maintain in notes.
  • Use checkboxes only for real tasks you plan to revisit.
  • Use separate cheat sheets for plugin-heavy syntax like Templater, Dataview, or Tasks queries.