markdown.style

HomeMeeting notes from Markdown to a page

Use cases

Meeting notes people who missed the call can actually use

Whoever reads these notes later was not in the room. Decisions, owners and dates need to stand out on their own, without anyone asking a follow-up question.

Open this example in the editorStart with your own

Decisions get numbers, not a paragraph

A decision buried in a paragraph gets missed on a second read. Number each one and put the reasoning in the same sentence, the way the sample does: what was decided, and why, in one line. Anyone skimming the notes later finds all four decisions without reading the agenda first, which matters most for the people who missed the call.

The action table is a csv fence, not hand-aligned pipes

A Markdown table with pipes needs a separator row and needs every column re-aligned by hand whenever a name gets longer. A csv fence skips both problems: one line per action item, no alignment, and adding an owner or a due date is one edit to one row.

If the action items started life in a spreadsheet, that export is already this shape. Paste the copied rows into the source pane and the editor wraps them in a csv fence automatically. An Undo button appears next to the pane, in case that paste was meant to stay as plain text.

Owners and dates stay with the task

Add an owner column and a due date column to the same fence, one of each per action item. The rendered table keeps them next to the task, not in a separate list a reader has to cross-reference. A date typed as plain text sorts however it was typed: the table does not reorder rows on its own. Put the soonest deadline first in the source if you want it to read first in the table.

Worked example

A 45-minute planning sync: agenda, numbered decisions, an action item table and a list of follow-ups.

# Onboarding flow: planning sync

- Date: 12 March, 45 minutes
- Attendees: Priya (PM), Dev (design), Sam (backend), Lena (frontend)
- Notes taken live by Priya

## Agenda

- Review drop-off data from last sprint (10 min)
- Decide on the welcome-email trigger (15 min)
- Scope the empty-state redesign (15 min)
- Quick wins for next sprint (5 min)

## Decisions

1. The welcome email sends 10 minutes after signup, not immediately, so it lands after the confirmation email.
2. The empty-state redesign ships behind a feature flag, off for existing accounts.
3. We drop the second onboarding tooltip; the drop-off data shows nobody reads it.
4. Sam owns the event schema change; Lena will not block on it to start the frontend work.

## Action items

```csv
Owner,Action,Due
Sam,"Add the ""email_sent"" event to the signup pipeline",18 March
Lena,Build the empty-state redesign behind a flag,21 March
Dev,"Deliver final copy for the empty state, including the button label",15 March
Priya,Write the flag rollout plan and share with the team,17 March
Sam,Update the analytics dashboard for the new event,20 March
```

## Parking lot

- Whether the welcome email needs a Spanish translation
- Renaming the "workspace" concept in the settings page
- A possible second onboarding path for team invites, not solo signups

## Follow-ups

- [x] Priya to book the 21 March review slot on the team calendar
- [x] Sam to confirm the event schema change with the data team
- [ ] Lena to share a first empty-state draft in the design channel
- [ ] Dev to send final copy to Lena by 15 March
- [ ] Priya to circulate these notes and the action item table

Rendered in the Minimal theme. Open it in the editor to change the theme or the text.

Follow-ups as a task list, ticked as they close

The sample's follow-up list uses - [x] and - [ ], rendered as checkboxes with two already ticked. Reusing the same document next week means checking off what got done and adding new lines underneath, so the follow-up list never needs rewriting from scratch.

A calm theme for something people read once

Minimal keeps the type quiet and the column narrow, which suits notes nobody is meant to linger on. Headings stay medium weight and links are underlined, so nothing on the page competes with the numbered decisions for attention. For a set of notes with a strong agenda and hard deadlines, Swiss is built for agendas, briefs and one-page summaries and reads more decisive on a screen.

Sending the notes and keeping the source

Copy styled HTML pastes the table and text into an email with their look intact. List markers may not survive that paste, so the numbered decisions can arrive unnumbered depending on the email client the reader opens it in. Print or save as PDF and Download .html both keep the numbering as written on the page.

Whichever export goes out, keep the .md file as the source. It stays smaller than any export. Download .md saves it exactly as written, ready to reopen next time this team meets and add the next set of decisions to.

Questions

What happens to the numbered decisions if I email the notes?

Copy styled HTML keeps the table and the text, but list markers may not survive the paste. A numbered decision list can lose its numbers when it lands in the reader's inbox. Exporting to PDF or downloading the HTML file keeps the numbers as written.

My action items come from a spreadsheet. Do I have to type them again?

Paste the exported rows into the source pane. The editor detects CSV-shaped text and wraps it in a csv fence for you automatically, with an Undo button if that was not what you wanted.

Does the action table need commas or semicolons, and what about a comma inside a field?

Either works: the delimiter is detected from the first line of the fence. A field with a comma in it just needs quotes around it, and the table still lines up correctly.

Where do the notes actually live once the meeting is over?

Nowhere but wherever you save them. Download .md saves the source exactly as written, and reopening it with Open or a drop onto the source pane brings back the same document.