Markdown is a plain-text writing system that uses simple symbols to format web content. This cheat sheet helps students remember the most common syntax for headings, bold text, links, images, lists, code, quotes, and tables. It is useful for class notes, README files, blogs, documentation, and online assignments.
Learning Markdown helps students write clearly without needing a complex editor.
The core idea is that readable text plus a few symbols becomes formatted content when rendered. Symbols like #, *, -, >, `, and []() tell the computer how to display the text. Spacing matters, especially for lists, code blocks, and tables.
A strong Markdown reference shows the syntax beside the rendered result so students can connect what they type to what readers see.
Key Facts
- A heading uses one to six # symbols before text, such as # Title for a level 1 heading and ### Section for a level 3 heading.
- Bold text uses two asterisks or underscores on each side, such as **important** or __important__.
- Italic text uses one asterisk or underscore on each side, such as *word* or _word_.
- A link uses the pattern [link text](https://example.com), where the visible words go in brackets and the URL goes in parentheses.
- An image uses the pattern , where the exclamation mark tells Markdown to display an image instead of a link.
- An unordered list uses -, *, or + before each item, such as - apples, and an ordered list uses numbers, such as 1. First step.
- Inline code uses single backticks, such as `print("Hello")`, and a code block uses three backticks before and after the code.
- A simple table uses pipes and a separator row, such as Name | Score followed by --- | --- and then Ana | 95.
Vocabulary
- Markdown
- Markdown is a lightweight markup language that turns plain text with simple symbols into formatted content.
- Syntax
- Syntax is the required pattern of characters that tells Markdown how to format text.
- Rendered Result
- The rendered result is the formatted version that readers see after Markdown is processed.
- Heading
- A heading is a title or section label created with one or more # symbols before the text.
- Inline Code
- Inline code is short code or command text placed inside a sentence using single backticks.
- Alt Text
- Alt text is a short description of an image that helps screen readers and appears if the image cannot load.
Common Mistakes to Avoid
- Forgetting the space after # in a heading is wrong because #Title may not render as a heading in some Markdown tools, while # Title is the standard form.
- Putting link parts in the wrong order is wrong because (https://example.com)[Example] will not create a normal link, while [Example](https://example.com) will.
- Using one backtick for a multi-line code block is wrong because single backticks are for inline code, while three backticks are used before and after longer code.
- Breaking table alignment with missing pipes is wrong because each row needs matching columns, such as Item | Price followed by --- | ---.
- Adding random indentation before normal text is wrong because Markdown may treat indented lines as code blocks instead of regular paragraphs.
Practice Questions
- 1 Write the Markdown syntax for a level 2 heading that says Science Notes.
- 2 Write Markdown that makes the word velocity bold and the word acceleration italic.
- 3 Write Markdown for a link with the visible text LivePhysics that goes to https://livephysics.com.
- 4 A classmate writes notes using plain paragraphs only. Explain why headings, lists, and code formatting make Markdown notes easier to read and maintain.
Understanding Markdown Syntax Reference
Markdown works because a renderer reads patterns in the source file and turns them into elements in a page. The same symbol can mean different things depending on its position. A star in the middle of a word may stay ordinary text, while stars around a complete word may create emphasis.
Blank lines often tell the renderer where one block ends and another begins. This is why a list can fail when items are pushed together or indented unevenly. If a symbol needs to appear as a real character, many Markdown tools let writers place a backslash before it.
Learning to notice the raw source is useful. It helps students find the small character or missing space that caused an unexpected result.
Good Markdown is more than making text look neat. Heading levels create an outline for the whole document. A main topic should come before its smaller sections, rather than choosing heading sizes only for appearance.
This structure helps readers scan long work. It matters for screen readers too, since many users move through a page by its headings. Link text should describe the destination clearly.
Words such as class rubric give more information than click here. Image descriptions should state the useful content or purpose of an image.
A description such as graph showing temperature rising over five days is more helpful than graph image. These choices make school work easier to use for more people.
Not every website supports exactly the same version of Markdown. A README on a coding site may support task lists, automatic web links, or special table features. A classroom website may support only basic formatting.
Tables are especially inconsistent because they are not part of every original Markdown standard. Before depending on an advanced feature, students should check the preview on the site where the file will be used. Code blocks need extra care.
Their contents are meant to stay unchanged, so indentation, quotation marks, and line breaks can matter. Some platforms accept a language name after the opening fence. This can add color to code and make examples easier to read, but it does not run the code or prove that it works.
A useful habit is to write the ideas first, then add structure in a second pass. Check that headings form a sensible path, list items have the same style, and links go to safe, relevant pages. Preview the document before submitting it.
Pay attention to blank lines around lists, quotes, tables, and code because these areas cause many errors. Keep lines of ordinary text reasonably short when possible, since the source file stays easier to read and edit. Markdown files are plain text, so they work well with version history tools.
A teacher or teammate can see exactly what changed between two versions. That makes Markdown practical for lab reports, project instructions, coding notes, and group documentation.