Markdown for Students Who Want Their Notes to Compound

Most markdown guides sell you on the wrong thing. They tell you markdown will make your notes prettier. Cleaner. More portable. Sure. Fine. Those are real benefits and also basically nobody changed their note-taking habits because of them.

Here is a better reason. Markdown is the format that lets your notes do work after you write them.

Specifically: when a note has structure — real headings, real lists, real definitions, real math — Fennie can turn it into a quiz or a flashcard deck in two clicks. When a note is a wall of text, you get a wall-of-text quiz that asks vague questions and accepts vague answers. The structure isn't decoration. It's the difference between notes that compound and notes that rot.

This guide walks through markdown the way it actually matters: every piece of syntax, plus a sentence about why it changes what Fennie can do with your note tomorrow.

The argument, in one paragraph

When you write ## Photosynthesis, you're telling the chunker "this is a unit." When you write **Calvin cycle**: the light-independent reactions..., you're telling the flashcard generator "this is a definition." When you wrap math in dollar signs, the equation renders cleanly on the card instead of looking like a string of characters someone copy-pasted from a forum. The syntax is the API between you and the system that's going to test you on this material later. Markdown is just how the API speaks.

Headings: # ##

Headings are the most important markdown feature, and most people use them wrong. They make every heading the same level, or they skip levels, or they use bold instead.

The rule:

• One # per note. The title.
• ## for major topics. A lecture probably has 3-6 of these.
• ### for subtopics inside those. Mechanism A, Mechanism B, etc.
• #### only if you really need it.

Why this matters when Fennie generates a quiz

The chunker reads heading levels. A note with one giant section produces a quiz that's all over the place — vague, broad questions because the system can't tell where one idea ends and another begins.

A note with five ## sections, each with two or three ### subsections, produces a quiz with focused clusters of questions. You'll get one or two questions per subsection. The quiz feels like it's testing what you actually studied, not throwing darts at a wall.

Concrete example. If your econ notes look like this:

You'll get a quiz that hits demand-pull vs cost-push as a distinct question, and another one on short-run vs long-run Phillips. Versus a note with no subheadings, where you get "explain inflation" and you write three sentences and the quiz has nothing specific to grade against.

Bold and italic

Bold for terms. Italic for emphasis or non-English words.

The pattern that pays off the most:

This is the cleanest possible signal that something is a definition. The flashcard generator picks these up almost perfectly. Term goes on the front of the card. Definition goes on the back. Done.

Compare:

Versus:

The first one becomes a clean flashcard. The second one becomes a flashcard that tests whether you can hand-wave about energy.

If you do nothing else with markdown, learn the bold-colon-definition pattern. It is worth more than every other syntax rule combined.

Lists

Bulleted lists for unordered things. Numbered lists for sequences and steps.

Why this matters

Lists become flashcards in a specific way. A numbered list of steps generates as "what's step 3?" or "list the steps in order." A bulleted list of features generates as "what are the features of X?"

If a list has more than about seven items, break it into sub-lists or split it into multiple sections. The system will try to test on a long list and you'll get a card that says "name all 12 cranial nerves" with no scaffolding. Six items, then six items, broken into two sub-sections, generates as two manageable cards.

Nesting works:

The two-space indent is what makes nesting work. One space won't do it. A tab might or might not, depending on the renderer. Two spaces, every time.

Math: dollar signs and double dollar signs

For STEM students this is the killer feature.

Inline math, in a sentence:

Block math, on its own line, centered:

Common things you'll actually use:

• Greek letters: \alpha, \beta, \pi, \Delta, \theta, \sigma
• Fractions: \frac{a}{b}
• Powers and subscripts: x^2, H_2O, x_{i+1}
• Roots: \sqrt{x}, \sqrt[3]{x}
• Sums and integrals: \sum_{i=0}^n, \int_a^b
• Limits: \lim_{x \to 0}
• Vectors: \vec{v}

Why this matters

Math written as plain text in your notes gets rendered as plain text on the flashcard. x^2 + 2x + 1 shows up in monospace, looking like code, and your brain doesn't recognize it as the math you've been doing all semester.

Math written in LaTeX gets rendered as actual math. $x^2 + 2x + 1$ shows up looking like the textbook. The flashcard feels like a math card, your brain recognizes the shape, you study faster.

For organic chemistry, biology, and anything with chemical formulas, the same logic applies. Subscripts, superscripts, arrows — all of it renders cleanly when wrapped in dollar signs. Without them you get a wall of digits and letters that's miserable to read.

Twenty seconds of LaTeX during note-taking saves you hours of squinting at flashcards later.

Code blocks

Code blocks aren't just for CS students.

The language tag after the opening backticks (python, javascript, sql, r, bash) gives you syntax highlighting. Use it.

But code blocks are also useful for:

• Chemical equations you don't want LaTeX-ified
• Pseudocode for algorithms
• Verbatim quotes from a textbook
• Anything where formatting matters and you don't want markdown to interpret asterisks or underscores

Why this matters

Code in fenced blocks generates as flashcards that preserve the exact formatting. The card shows up looking like code, monospace and indented, and you can read it. Code typed inline as a paragraph generates as a flashcard with weird line breaks and lost indentation.

For a CS student studying for a midterm, this is the difference between a deck full of unreadable cards and a deck you can actually drill through on the bus.

Tables

Tables are how you should write any comparison. Drug A vs drug B. Sympathetic vs parasympathetic. Civil law vs common law. If you find yourself writing the same sub-headings under multiple sections — Definition, Example, Side Effects, Uses — you should be using a table.

Why this matters

Tables generate flashcards row by row. The header row becomes the question template. Each row becomes a card. "What happens in phase G1?" "Growth." "What happens in phase S?" "DNA replication." Clean, predictable, drillable.

A wall of paragraphs comparing the same things across phases generates a vague flashcard that asks "describe the cell cycle" and then you write a paragraph and there's nothing to check against.

Blockquotes

For direct quotes from sources. Especially useful in humanities classes where the exact wording of a passage matters.

A pattern I like:

This three-part structure generates very rich flashcards because the primary text is anchored to your interpretation, and the system can ask either direction: give the quote, ask the interpretation; give the interpretation, ask the quote.

Links and internal references

Useful for keeping the source attached. The flashcard won't quiz you on the URL, but the link stays in the note for when you need to revisit.

Internal note links — referencing one Fennie note from another — are useful for building a web of connected ideas. If your enzyme kinetics note links to your Michaelis-Menten note, both notes are stronger, and Memory tracks them as related.

Task lists

Task lists are checkboxes. Useful for "things I need to come back to" inside a note. Not study material per se — but they pair well with Fennie's task and calendar system, because anything left unchecked in a note can become its own task.

A worked example: a real lecture note

Here's what a usable, Fennie-ready note looks like for a single chemistry lecture. Not perfect, not pretty, but structurally good.

Click "generate flashcards" on this note, and you get:

• 4 vocabulary cards (acid, base, conjugate acid, conjugate base)
• 1 example card with the HCl reaction
• 2-3 cards about strong vs weak (from the table)
• 2 formula cards (one for strong, one for weak)
• 1 worked-problem card

That's roughly 10-12 cards from a single lecture. Spaced repetition handles the rest. Three weeks from now, the night before the midterm, you've actually seen the Bronsted-Lowry definitions twelve times instead of twice.

What not to do

A few markdown patterns that look fine but generate terrible study material:

Walls of text under one heading. If you wrote 800 words under ## Cell Biology, break it up. Add subheadings every 100-200 words. Use bullet points to break up paragraphs that are really lists in disguise.

Inconsistent definition formatting. If half your terms use **Term**: definition and half use "A term is when..." you'll get half clean flashcards and half garbage flashcards. Pick a pattern.

Math written as plain text. Already covered, but worth repeating. Use dollar signs every time, even for simple stuff like $x^2$.

Lists with 20 items. Break them up. Group them. Six is comfortable, ten is the upper limit, twenty is unstudiable.

Headings used as decoration. ### Important! is not a real heading. It's a vibe. Real headings name a topic.

The point

Markdown is not about making your notes look professional. It's about writing notes structured well enough that the next step happens automatically. You write the note in class. You clean it up that evening. You click "generate flashcards." You click "generate quiz." Tomorrow's plan has both of those waiting for you.

That whole loop only works if the note has shape. Markdown is how you give it shape.

Pick one note from this week. Open it. Add three subheadings. Convert four definitions to the bold-colon pattern. Put two equations in dollar signs. Generate the deck. See the difference.

Start using Fennie