DocsOrderbook
Learning Path00 Start Here01 Big Picture
IntroductionWhat Is an Order BookBids and AsksSpread and Mid PriceLimit OrdersMarket OrdersDepth and Liquidity
Matching Engine Basics02 Core Domain03 Matching Flow05 Guided Exercises06 Visual Guide07 Why This Design08 Performance Bridge
ArchitectureTechnical ArchitectureUI Notes and Terminal Ideas
Engine Performance NotesPerformance
Milestones
Glossary
LearnTerminal
DocsArchitecture

UI Notes and Terminal Ideas

Product and design notes for building a better trading-learning interface.

UI Notes and Terminal Ideas

This project is not trying to be just a pretty dashboard.

It is trying to be:

  • a trading terminal
  • a learning system
  • a quant-dev study environment

What should stay primary

The primary surfaces should be:

  • chart
  • orderbook
  • order form

Everything else should support those.

What belongs in the learning area

The lower learn widget is a good place for:

  • glossary
  • docs
  • lessons
  • event log
  • future tutorial entry points

What should not dominate the UI

Avoid letting these take over the terminal:

  • redundant badges
  • oversized explanatory blocks
  • duplicate views that show nearly the same state

Best product split

  • **terminal mode**: compact, instrument-like, market-focused
  • **learn mode**: definitions, event explanation, guided reading

Future tutorial ideas

Later, tutorial mode could highlight:

“This order crossed the spread, so it executed immediately against the resting ask.”

That would turn the app into a stronger study tool than static docs alone.

PreviousNext
On This Page5
What should stay primaryWhat belongs in the learning areaWhat should not dominate the UIBest product splitFuture tutorial ideas