Posting guide — markdown, math, code, images

How to format posts on QuantFinancePrep. Everything here uses standard markdown — if you have written a GitHub README.md, you already know most of it.

Text

  • **bold**bold
  • *italic*italic
  • `inline code`inline code
  • > quoted line → quoted block
  • Use ## and ### for headings. Avoid # — it collides with the topic title styling.

Code blocks

Wrap code in triple backticks with a language tag. The language tag enables syntax highlighting.

  ```python                                                                                                    
  def max_drawdown(prices):                             
      peak = prices[0]                                                                                         
      best = 0                                          
      for p in prices:
          peak = max(peak, p)                                                                                  
          best = max(best, peak - p)
      return best                                                                                              
  ```                                                   

Other useful tags: r, sql, cpp, bash, json.

Math

Inline math: $x^2 + y^2 = r^2$x^2 + y^2 = r^2

Display math — wrap in $$ … $$ on their own lines:

$$                                                        
\mathbb{E}[X] = \int_{-\infty}^{\infty} x \, f(x) \, dx
$$

Rendered:

\mathbb{E}[X] = \int_{-\infty}^{\infty} x \, f(x) \, dx

Standard LaTeX inside $…$ or $$…$$. Greek letters, subscripts, fractions, matrices all work.

Images

Three ways, in order of convenience:

  1. Drag and drop the image into the editor.
  2. Paste from clipboard (screenshot → Ctrl+V or Cmd+V).
  3. Click the image icon in the editor toolbar and upload.

Images are hosted on the forum. Max size is shown in the upload dialog. For charts, PNG is preferred over JPG.

Links

  • [visible text](https://example.com)visible text
  • A bare URL on its own line may auto-expand into a preview card.

Tables

Use pipes | to separate columns and a row of dashes --- to mark the header:

| Metric  | Value |                                       
|---------|-------|
| Sharpe  | 1.8   |                                                                                              
| Sortino | 2.4   |

Rendered:

Metric Value
Sharpe 1.8
Sortino 2.4

Column alignment: put a colon in the dash row — :— left, —: right, :—: center.

Same trick as math: the markdown language tag keeps the first block literal; the unfenced table below renders normally. Drop in replacing the current Tables section.

Tips

  • Preview before submitting — the right pane shows exactly how the post will render.
  • For long posts, use headings so readers can scan.
  • Reply directly to a specific post using the reply icon on that post, not the bottom reply button — it threads correctly.