Skip to content

Guides and resources for AI engineers: an agents course, five handbooks, a hands-on second-brain project and a vetted reading list.

resources: graph and publishing repos

undefined-ui5af61ba4e439
diff --git a/README.md b/README.md
index 0025096..2636994 100644
--- a/README.md
+++ b/README.md
@@ -225,6 +225,31 @@ Worth reading before writing your own page contracts.
More context on each: [resources/skills.md](resources/skills.md).
+## Graph and publishing repos
+
+Beyond implementations of the pattern itself.
+
+**Graph views for Obsidian.** [Juggl](https://github.com/HEmile/juggl) for an
+interactive workspace graph with typed edges,
+[ExcaliBrain](https://github.com/zsviczian/excalibrain) for a structured
+mind-map derived from your links and Dataview fields, and
+[Breadcrumbs](https://github.com/michaelpporter/breadcrumbs) for typed links plus
+trees, matrices and Mermaid views over them.
+
+**GraphRAG.** [microsoft/graphrag](https://github.com/microsoft/graphrag) is the
+reference implementation;
+[nano-graphrag](https://github.com/gusye1234/nano-graphrag) is the same idea in
+about 1,100 readable lines; [LightRAG](https://github.com/HKUDS/LightRAG) adds a
+vector layer for cheaper incremental updates.
+[Awesome-GraphRAG](https://github.com/DEEP-PolyU/Awesome-GraphRAG) covers the
+rest of the landscape.
+
+**Publishing.** [Quartz](https://github.com/jackyzha0/quartz) turns a vault into
+a static site with backlinks, local graph and search.
+
+Notes on each, and how to judge a repo in this ecosystem:
+[resources/repositories.md](resources/repositories.md).
+
## Contributing
Corrections, resources and real examples are welcome. Read
diff --git a/resources/README.md b/resources/README.md
index a61f67c..cf876c6 100644
--- a/resources/README.md
+++ b/resources/README.md
@@ -6,6 +6,8 @@ that exists only in secondary coverage is marked as such.
- [Tools](tools.md). Editors, capture, agents, graph and search
- [Skills and implementations](skills.md). Agent skills and open-source builds
of this pattern
+- [Repositories](repositories.md). Graph plugins, GraphRAG implementations,
+ publishing
- [Reading](reading.md). The ideas behind the pattern
- [Papers](papers.md). Retrieval, graphs and long-context research
diff --git a/resources/repositories.md b/resources/repositories.md
new file mode 100644
index 0000000..81ee9b3
--- /dev/null
+++ b/resources/repositories.md
@@ -0,0 +1,78 @@
+# Repositories
+
+Beyond the implementations of this pattern in [skills.md](skills.md). Every link
+here was opened and checked; anything I could not verify is named without a link
+rather than guessed at.
+
+## Graph views for Obsidian
+
+The built-in graph view is a viewer with no notion of relationship types. These
+replace it when you want the graph to do work.
+
+- **[HEmile/juggl](https://github.com/HEmile/juggl)**. An interactive, stylable,
+ expandable graph built on Cytoscape.js. Its workspace mode is the real feature:
+ you build a graph of just the nodes relevant to what you are working on, expand
+ and hide selectively, pin positions, and save it for later. Supports link types
+ on edges, which plain Obsidian does not. Has an API other plugins build on.
+- **[zsviczian/excalibrain](https://github.com/zsviczian/excalibrain)**. A
+ structured mind-map of the vault rather than a force-directed cloud. It derives
+ five relationship types from your links, Dataview fields, tags and frontmatter:
+ parents, children, friends, other friends, siblings. Requires Dataview and
+ Excalidraw. The closest thing to [typed
+ links](../docs/05-graphs/typed-links.md) with no extra work from you.
+- **[michaelpporter/breadcrumbs](https://github.com/michaelpporter/breadcrumbs)**.
+ Typed links plus navigation over them: breadcrumb trails, tree and matrix
+ views, Mermaid and Markmap rendering, export to Canvas. Reads typed frontmatter
+ links, tags, lists, folder notes and Dataview queries, and derives implied
+ relations. Maintained by michaelpporter since May 2026, originally by
+ SkepticMystic.
+
+## GraphRAG implementations
+
+Read these if you want to see what an automated version of the graph looks like
+before deciding you do not need one. See
+[GraphRAG and where it fits](../docs/05-graphs/graphrag.md).
+
+- **[microsoft/graphrag](https://github.com/microsoft/graphrag)**. The reference
+ implementation of the [paper](papers.md). Entity extraction, community
+ detection, community summaries, global and local search.
+- **[gusye1234/nano-graphrag](https://github.com/gusye1234/nano-graphrag)**. The
+ same idea in roughly 1,100 lines, written to be read and modified. This is the
+ one to open if you want to understand the pipeline rather than run it.
+ Pluggable storage: networkx by default, Neo4j available.
+- **[HKUDS/LightRAG](https://github.com/HKUDS/LightRAG)**. A dual-layer approach
+ holding both a knowledge graph and vector embeddings, aimed at cheaper
+ incremental updates than the original. Published at EMNLP 2025. Structurally
+ based on nano-graphrag.
+- **[DEEP-PolyU/Awesome-GraphRAG](https://github.com/DEEP-PolyU/Awesome-GraphRAG)**.
+ A curated list of surveys, papers, benchmarks and open-source projects in this
+ area. The right starting point if you want the landscape rather than one tool.
+
+Also worth knowing by name: Graphiti and Cognee, both graph-based memory layers
+for agents rather than knowledge bases for people. Different problem, adjacent
+techniques.
+
+## Publishing
+
+- **[jackyzha0/quartz](https://github.com/jackyzha0/quartz)**. Publishes a vault
+ as a static site with backlinks, link previews, a local graph and full-text
+ search. Understands both wikilinks and markdown links, which is the thing to
+ check in any publishing tool. Docs at
+ [quartz.jzhao.xyz](https://quartz.jzhao.xyz/).
+
+ One caveat that applies to every publishing tool: check how it handles links to
+ unpublished pages before you publish anything. See [publishing and
+ export](../docs/08-outputs/publishing-and-export.md).
+
+## How to judge one of these
+
+Two questions answer most of it.
+
+**Does it own your data or read it?** Anything that reads your markdown and
+writes derived output is safe to try and safe to abandon. Anything that becomes
+the only place a piece of knowledge lives has taken the portability you chose
+markdown for.
+
+**Is it maintained?** Check the commit history, not the star count. This
+ecosystem produces a lot of repos in the weeks after a popular gist, and most of
+them stop within a month.