Trading Notes
Home/Journal/How to Add Notes to This Site
Back to Journal

How to Add Notes to This Site

A complete guide to adding journal entries, strategies, lessons, and analysis to the trading site. Covers frontmatter fields, MDX components, and the git workflow.

4 min read

Overview

This site is a static Next.js app. Content lives in a separate git repo (trading-journey) mounted as a submodule. You write .mdx files, commit them, and the site picks them up — no database, no CMS, no login.

Folder Structure

Each section maps to a folder:

trading-journey/
├── journal/        # Daily trade logs and weekly recaps
├── strategies/     # Setups, playbooks, rules-based strategies
├── analysis/       # Market analysis, chart studies, macro notes
├── lessons/        # Mistakes, key takeaways, things to avoid
└── psychology/     # Mindset, discipline, emotional management

Put your file in whichever folder matches what you're writing.

File Format

Every file is .mdx — standard Markdown with optional React components.

Filename Convention

YYYY-MM-DD-short-description.mdx

Examples:

  • 2026-03-04-btc-long-ema-pullback.mdx
  • 2026-03-10-week-2-recap.mdx
  • risk-management-rules.mdx (evergreen docs don't need a date)

Required Frontmatter

---
title: "Your Title Here"
slug: your-slug-here
publishedAt: "2026-03-04"
summary: "One sentence shown on cards and in search. Make it useful."
---

Optional Frontmatter

# Categorisation
tags: [crypto, btc, ema-pullback]
 
# Trading-specific fields
ticker: BTC/USD
tradeType: long        # long | short | swing | analysis
outcome: win           # win | loss | open | scratch
pnl: 2.4              # in R multiples or dollars
 
# Display options
pinned: true           # shows first in trending
published: false       # draft — hidden from site until true

Writing Trade Journal Entries

For individual trade logs, aim to capture:

---
title: "BTC Long — EMA Pullback 2026-03-04"
slug: btc-long-2026-03-04
publishedAt: "2026-03-04"
summary: "Entered long on BTC at the 20 EMA on 1H after 4H uptrend confirmed."
tags: [crypto, btc, ema-pullback, paper-trade]
ticker: BTC/USD
tradeType: long
outcome: win
pnl: 2.1
---
 
## Setup
 
[Describe what you saw. Trend direction, key level, pattern.]
 
## Trade Details
 
| Field   | Value         |
|---------|---------------|
| Entry   | $62,400       |
| Stop    | $61,800       |
| Target  | $63,600       |
| Risk    | 1% of account |
| R:R     | 1:2           |
 
## Execution
 
[What happened after entry? Did you follow the plan?]
 
## Outcome
 
[Win/loss, how much in R, what moved price.]
 
## Emotions
 
[How did you feel? What did you want to do vs what you actually did?]
 
## Lesson
 
[One concrete thing to take into the next trade.]

MDX Components

You have access to a Callout component for highlighted notes:

<Callout type="info" title="Key Insight">
The act of writing your thesis before entering forces clarity.
</Callout>
 
<Callout type="success" title="What Worked">
Holding through the pullback and trusting the higher TF trend.
</Callout>
 
<Callout type="warning">
Always set your stop before you enter. Never move it wider.
</Callout>
 
<Callout type="error" title="Mistake">
Entered without waiting for candle close. Chased the move.
</Callout>

Standard Markdown also works: tables, code blocks, blockquotes, bold, lists — all render correctly.

Git Workflow

The content repo is at products/trading/content/ inside the main monorepo.

Adding a new note

# Navigate to the content repo
cd ~/projects/worktree/tracker/multiple-dbs-apis/products/trading/content
 
# Create your file
# (use your editor — nvim, cursor, whatever)
nvim journal/2026-03-04-my-trade.mdx
 
# Commit and push
git add .
git commit -m "journal: BTC long EMA pullback"
git push

The dev server hot-reloads immediately. No build step needed locally.

Updating the submodule pointer (after pushing content)

The main monorepo tracks a specific commit of trading-journey. After pushing content, update the pointer so the deployed site picks it up:

cd ~/projects/worktree/tracker/multiple-dbs-apis
 
# Stage the updated submodule ref
git add products/trading/content
git commit -m "chore(trading): update content submodule"
git push

This triggers the CI pipeline which rebuilds and redeploys the static site.

Sections at a Glance

SectionUse it for
JournalIndividual trade logs, weekly recaps, daily observations
StrategiesDocumented setups with rules, entry/exit criteria, backtest results
AnalysisMarket structure analysis, sector notes, macro observations
LessonsMistakes made, rules broken, things never to do again
PsychologyEmotional patterns, mindset notes, reflections on discipline

Tips

  • Write immediately after the trade — memory fades fast, emotion is still raw
  • Be honest about losses — the journal is only useful if it's accurate
  • Grade your execution, not the outcome — a losing trade with perfect execution is an A; a winning trade where you broke rules is a C
  • One lesson per entry — specific and actionable beats vague reflection
  • Use tags consistently — makes it easier to find patterns later (e.g. always tag revenge-trade when you break the rules)