Architecture Notes Index

$#! · 0-9 · A · B · C · D · E · F · G · H · I · J · K · L · M · N · O · P · Q · R · S · T · U · V · W · X · Y · Z

A
	Assumptions, NaturalDocs::SourceDB
C
	CSS Structure
F
	File Parsing
I
	Internal Overview, NaturalDocs::Settings
N
	Named Directories, NaturalDocs::Settings
	NDMarkup
R
	Removed Directories, NaturalDocs::Settings
S
	Symbol Management
T
	The Idea, NaturalDocs::SourceDB
	Title,Package,and Symbol Behavior, NaturalDocs::Parser::ParsedTopic

SourceDB is built around certain assumptions.

It’s important to understand the internal HTML file structure and styles in order to design your own CSS style for Natural Docs.

This is the architecture and code path for general file parsing.

Ever since Natural Docs introduced multiple input directories in 1.16, they’ve had to be named.

A markup format used by the parser, both internally and in NaturalDocs::Parser::ParsedTopic objects.

Directories that were part of the previous run but aren’t anymore are still stored in the package.

This is the architecture and code path for symbol management.

For quite a while Natural Docs only needed SymbolTable.

Title, package, and symbol behavior is a little awkward so it deserves some explanation.