---
title: "Choose the format for the work."
description: "Use Markdown where readable, portable writing helps—and recognize when another format fits better."
canonical: https://editmd.app/learn/lessons/formats/
markdown: https://editmd.app/learn/lessons/formats.md
status: pre-release, waiting list open
generated: editmd-website
---

# Choose the format for the work.

Lesson 02 of 12 in Markdown School. Use Markdown where readable, portable writing helps—and recognize when another format fits better.

## Begin with what the document must do

Imagine three tasks: explain a project, calculate a monthly budget and design a print brochure. Each has a different requirement. For the guide, headings, paragraphs and links are the main work. For the budget, calculations matter. For the brochure, precise placement matters.

Our practical recommendation: use Markdown for structured prose; use a spreadsheet when formulas and data operations dominate; use a layout tool when exact page composition is the task. This is a choice about the work, not a ranking of formats.

## A useful project introduction

```markdown
# Garden guide

A shared reference for our neighbourhood garden.

## Start here

Read the planting notes, then choose one task.

## Get involved

Bring an idea to the next garden meeting.
```

A README commonly introduces a project, explains its usefulness and helps people get started. The example above is deliberately small. A real project may also need installation requirements, usage examples, contribution guidance and support information. [GitHub’s README guidance](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes).

## Source and delivery can differ

You can write in Markdown and deliver another format. Keep the `.md` file as your editable source, then choose the output for the recipient. A PDF is a useful reading copy. A word-processing document may fit a colleague’s editing workflow. The [editmd export guide](/docs/exports/) explains what each conversion preserves.

## Portability has a boundary

CommonMark defines a core syntax. GitHub Flavored Markdown adds features such as tables and task lists. Mermaid diagrams and math depend on additional renderer support. Check the destination rather than assuming every preview will look the same. [CommonMark specification](https://spec.commonmark.org/), [GFM specification](https://github.github.com/gfm/).

## Choose your first project

Write a purpose statement and explain your format choice in the practice area. Two hashes and a space make a section heading, such as `## Purpose`; [the headings lesson](/learn/lessons/headings/) explains heading levels. For a starter you can keep, the [school home](/learn/#take-a-project-with-you) includes a complete meeting-notes file and README.

## Exercise

Write ## Purpose and ## Why Markdown. Under each heading, explain the document you want to create and why Markdown fits. The check confirms headings; you judge the choice.

## Takeaway

Choose the format around the next person or tool that will use your work.

Related guide: https://editmd.app/docs/exports/. All lessons: https://editmd.app/learn.md