Two structures carry most of the weight in real notes: checkboxes for the work, and tables for the comparisons. Markdown Studio treats both as first-class blocks — tasks render as checkboxes you can actually click, and tables come with a floating menu for rows and columns — while saving each one as textbook Markdown that any other tool reads without complaint.
Task lists: checkboxes that mean it
A task list is a list of items with a checkbox each. In Markdown Studio:
- Type the slash key on an empty line and choose Task list.
- Type the first task and press Enter — the next checkbox appears automatically.
- Click a checkbox to mark the task done; click again to reopen it.
- Nest tasks by indenting, and reorder them with the block drag handle.
On disk, a completed task saves as the standard checked-box syntax and an open one as the empty box, so your to-do list stays legible in GitHub issues, VS Code and every other Markdown consumer. This is what makes the format genuinely useful for project notes: the file is both a rendered checklist and a plain-text record anyone can grep.
Tables: grids without pipe alignment
A Markdown table is four things — a header row, a separator, and data rows — and hand-writing one is where most people give up on the syntax. In the editor you never touch the punctuation:
- Type the slash key and choose Table. A grid appears with a header row and two body rows.
- Fill the header, press Tab to move across, and Enter to drop to the next row.
- Click inside the table to raise the floating TableMenu.
- Use the TableMenu to insert or delete rows and columns, and to set alignment per column.
The table grows and shrinks by click, and the underlying file always holds a proper pipe-and-dash table — aligned or ragged in the source, the rendered result is identical. Wide tables scroll horizontally rather than wrapping, so a ten-column grid stays readable in the editor.
The TableMenu in detail
The floating menu appears whenever the cursor is inside a table:
| Control | What it does |
|---|---|
| Insert row above / below | Adds a row adjacent to the current one |
| Delete row | Removes the current row and its contents |
| Insert column left / right | Adds a column beside the current cell |
| Delete column | Removes the current column |
| Alignment | Sets left, center or right per column |
Combined with Tab-navigation for filling cells, tables stop being the reason people avoid Markdown tables.
Quotes and headings around them
The same block philosophy covers the rest of the structure:
- Blockquotes — insert from the slash menu or type the angle-bracket shorthand; the block renders with its quote styling and saves as standard Markdown.
- H1 through H6 — apply from the slash menu or the toolbar; the heading level is a property of the block, so promoting or demoting is one click rather than re-typing hashes.
A weekly note, for example, reads top to bottom as: an H1 title, an intro paragraph, a blockquote carrying the week's theme, a task list for the work, and a table of metrics — five blocks, no syntax, all portable.
A weekly note, assembled for real
To make that concrete, here is the shape most people converge on after a few weeks:
- H1 title with the week — "Week 36: migration cutover".
- Blockquote for the one sentence that defines the week's priority.
- Task list — the three to seven things that must move; everything else goes in plain bullets so the checkboxes stay meaningful.
- Table — two columns, metric and value, filled in on Friday.
- H2 "Decisions" — short paragraphs recording what was agreed and why.
The pattern works because each structure does one job: checkboxes for commitments, a table for numbers, prose for reasoning. When the note is done, the same file serves three audiences — you, reading the rendered checkboxes; git, diffing the plain text; and the team, receiving the exported DOCX with a real Word table inside.
Small behaviors worth knowing
A few details make the difference between using these blocks and being fluent in them:
- Tab and Shift+Tab indent and outdent list items, including tasks — the nesting follows the standard Markdown two-space convention on disk.
- Enter on an empty list item exits the list rather than adding another empty bullet, which is how lists end cleanly.
- Clicking a checkbox is recorded the moment it happens — autosave keeps the file honest even mid-meeting.
- Column alignment set in the TableMenu is written into the separator row, so centered columns survive in every other Markdown renderer.
- The drag handle moves list items, table rows' neighbors and headings alike — restructuring never means re-typing structure.
None of these need learning up front; each announces itself the first time the situation arises. Together they are why the blocks feel less like syntax with training wheels and more like an ordinary editor that happens to write perfect Markdown.
What to explore next
- Slash commands — insert every block type from one menu.
- Code blocks — fenced code with syntax display and copy.
- Frontmatter and properties — YAML metadata above the content.
- Export to DOCX — how tables and tasks survive the trip.