Document ​

"Document" is everything in a .gg file that isn't an icon, connector, region, or note — the diagram-level settings (columns, rows, theme, icons) carried inside one or more doc { … } statements.

The doc { … } statement ​

doc {
  cols: 3, rows: 3,
  theme: { primary: '#1e3a5f', accent: '#e8792f' },
  icons: {
    logo: './assets/logo.svg',
  },
}

Everything inside the braces is JSON5 (not strict JSON). You get:

• Unquoted keys — cols: 3 is fine; no need for "cols"
• Trailing commas — every list/object can end with one
• // comments — // inside JSON5
• Single-quoted strings — '#1e3a5f' works as well as "…"

Strict JSON is a subset of JSON5, so anything you'd write in plain JSON parses unchanged.

Multiple doc blocks per file ​

A single .gg can contain as many doc blocks as you want; they're merged in source order (later values win). Arrays concatenate; scalars deep-merge:

doc { cols: 4 }

# … DSL …

doc {
  theme: { accent: '#d97706' },
}

Both the cols and theme.accent values end up in the final DiagramDef. See Merging for the full rules.

The five commands ​

Every .gg line starts with one of these keywords, except connectors (which take the <id> <arrow> <id> shape):

Connectors never start with a keyword — Gridgram detects them by the arrow in position 2.

What can go in a doc body ​

Every top-level field of DiagramDef is accepted:

Comments ​

.gg supports line comments with # or //:

# section: public layer
icon :web @A1 tabler/world "Web"   // externally visible

Where to next ​

• Grid — cols / rows / cellSize / auto-inference
• Merging — multiple doc blocks, deep merge, DSL vs JSON tradeoffs