Editor Syntax Reference

Use this page when you want a quick formatting example while writing in Orbit.

Common shortcuts

What you want	Type
Heading	`# Heading`
Second-level heading	`## Heading`
Bullet list	`- Item`
Ordered list	`1. Item`
Task list	`- [ ] Task`
Quote	`> Quoted text`
Inline code	`code`
Code block	Three backticks before and after the code
Wiki link	`[[Note title]]`

# Project Plan
## Goals
### Risks

Use headings before a note gets long. Headings make tables of contents and AI client navigation easier to follow.

- First idea
- Second idea

1. First step
2. Second step

- [ ] Follow up with the owner
- [x] Confirm the launch date

Use task lists for actionable work. Use normal lists for notes, requirements, and ideas.

| Decision | Owner | Status |
| --- | --- | --- |
| Pick launch date | Maya | Open |
| Draft customer note | Lee | Done |

Use tables for decisions, owners, status, comparisons, and lightweight registers.

[[Customer Escalation Playbook]]

[Microsoft 365 admin center](https://admin.microsoft.com)

Use wiki links for Orbit notes. Use normal links for external websites or Microsoft 365 locations.

```bash
npm run build
```

Add a language name after the opening backticks when you want syntax highlighting.

```mermaid
flowchart LR
  Customer --> Support
  Support --> Orbit
  Orbit --> SharePoint
```

Use Mermaid for simple flows, sequences, ownership paths, and architecture sketches.

Use image actions for screenshots and diagrams. Use video links for demonstrations, training, and recordings that need written context nearby.

Before sharing, confirm images and videos are accessible to the intended audience.