Problem
The trading concepts I rely on were spread across books, PDFs, and one-off notes.
- Market Profile and auction-market theory live in dense source material.
- Highlights and summaries did not share one structure.
- Pre-session review meant reopening multiple files and guessing where I left off.
The information was not missing — it was fragmented.
What I needed before a session was a single place to re-read the frameworks in the same language I use when reviewing structure, not a hunt through folders.
Goal
Build a personal reference wiki for trading theory — readable, linkable, and stable.
The wiki needed to:
-
Hold long-form concept pages (auction mechanism, value, timeframe participants).
-
Use consistent sectioning so each article reads the same way.
-
Surface important distinctions without burying them in prose.
-
Link related topics so one concept leads to the next.
-
Stay fast to open on desktop before the session.
The aim was reference clarity for live trading prep, not a blog or course platform.
Features
Topic-organized articles
Trading concepts grouped by subject — e.g. auction market theory, timeframe participants, price–time–value — each as a dedicated reference page.
Structured long-form layout
Multi-part articles with anchored sections, tables, and a predictable reading order so dense theory stays scannable.
Distinction callouts
Important and note-style emphasis for ideas that are easy to misread in the heat of a session — initiative vs responsive activity, structure vs time vs logic.
Related-article navigation
Cross-links at the end of each page so one framework connects to the next without leaving the wiki.
Source attribution
Concept pages tied back to primary references (e.g. Jim Dalton’s Mind Over Markets) so the wiki stays honest reference material, not improvised theory.
System
Source material
Books and notes on Market Profile and auction-market theory — the raw concepts worth keeping in one operating reference.
Structure
Break each framework into parts, tables, and callouts that match how I actually review before a session.
Publish
Deploy as a static wiki on Vercel — always available, no login, fast to open from any machine.
Review loop
Use before the open to re-read the two big questions, timeframe dynamics, and value logic — then return to the same pages after the session when something needs a second pass.
Snapshots
