Extended Syntax / Tables
Tables
Tables are great for answers readers need to compare at a glance: what changed, who owns it, and what still needs work.
Basic Syntax
Use pipes and separator rows to build a compact status table:
| Page | Status | Owner |
|------|:------:|------:|
| Homepage | Rewritten | Albert |
| Intro | Editing | Docs |
| Syntax Pages | In Progress | You | Alignment
Alignment is useful when each column has a clear role, such as label, state, and priority:
| Page | Status | Priority |
|:-----|:------:|---------:|
| Headings | Rewritten | High |
| Links | Rewritten | High |
| Images | Pending | Medium | Preview
| Page | Status | Priority |
|---|---|---|
| Headings | Rewritten | High |
| Links | Rewritten | High |
| Images | Pending | Medium |
Writing Tips
- Keep each cell focused on one piece of information.
- Use short, consistent status labels so readers can scan down the column quickly.
- If the content reads more like explanation than comparison, a paragraph or list is usually better.
- Wide tables are fine when they truly add value, but do not force every chunk of structured content into a grid.
Comments
Comments are currently unavailable.
Enable GitHub Discussions for this repository and complete the giscus configuration to turn comments on.