References — bi-01 Navigating Chromium

Primary sources first. In-tree Chromium docs beat any external source, including these modules.

Chromium Code Search — the primary tool. Learn f: (path), c: (content), sym: (symbol), and -f:test to exclude tests.
Chromium source layout
Blink renderer README — the directory map you will use most.

Getting the source

Get the code (all platforms)
macOS build instructions · Linux
depot_tools tutorial
You do not need a full checkout for most of this track. Code Search plus a stock Chrome covers bi-01–bi-05 and bi-07–bi-11.

Reading conventions

Chromium C++ style guide
Blink C++ style
OWNERS files — the fastest way to learn who owns a subsystem and where its boundaries are.

Archaeology

Chromium commit history · Gerrit code review
git log -S"<string>" and git blame on a specific file are usually faster than searching the issue tracker for why a line exists.

bi-00 — Roadmap
bi-06 — Chromium C++ for frontend engineers — the language subset you need to read what you find
bi-14 — Contributing — where navigation becomes a patch

When a claim here proves stale, record it in PROGRESS.md section 7.