Obsidian Graph View

Obsidian Graph View

Create an Obsidian-like graph visualization from structured note/book data.

Default Output

Produce three files when possible:

• *.png for direct viewing and sharing
• *.svg for editable vector output
• *.html for browser re-rendering

Prefer PNG dimensions around 1800 x 1300 unless the user asks otherwise.

Visual Rules

• Put higher-weight nodes closer to the center.
• Push lower-weight nodes to outer rings.
• Use a spherical / ball-like node style with radial glow.
• Use different colors for different main Trails / note-sequence lines.
• If a node belongs to two Trails, render it as a two-color taiji-like sphere to show a note-sequence crossing point.
• Keep labels in Traditional Chinese readable: use large PingFang TC / Heiti TC / system CJK fonts, white text, dark translucent label boxes, and avoid placing labels directly on dark edges.
• Use a dark Obsidian-like background.
• Use node area, not radius, to represent weight. If the user says "放大兩倍面積", double the computed node area.
• Use semantic Trail colors rather than only node-type colors when main lines are available.
• Prefer undirected soft lines for Obsidian-style graph view; use arrows only if the user asks for directional semantics.
• Keep top-node count configurable. If the user corrects the count, update the graph and file names accordingly.

Data Mapping

For EPUB/project-note JSON:

• toc[] becomes chapter or directory nodes.
• index[] becomes keyword nodes.
• index[].links[] becomes keyword-to-chapter edges.
• toc[].cjk_count, keyword weight, and index link weights contribute to node size.
• chunks[].keyword_backlinks[] can be used to enrich link weights.

For generic graph JSON: