Obsidian Graph View Reimagined Full K-Plex Walkthrough & Demo

Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo ![rw-book-cover](https://d34adp677peecb.cloudfront.net/static/images/article4.6bc1851654a0.png) 🔗 **Source:** [Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo](https://www.youtube.com/watch?v=XIq8uf8OaNI) > [!note]+ Document Notes > tags: [obsidian, graph-view, personal-knowledge-management, knowledge-graphs, note-linking, plugin-demo] > author: Zsolt's Visual Personal Knowledge Management > source: Zsolt's Visual Personal Knowledge Management (YouTube) > reference: https://www.youtube.com/watch?v=XIq8uf8OaNI > date created: 2026-10-12 11:15 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo >  ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--obsidian-graph-view-reimagined-full-k-plex-walkthrough--demo) ## 📝 Summary - **What happened.** Zsolt's Visual Personal Knowledge Management published a 56:08 walkthrough on 2026-10-10 of K-Plex, an Obsidian plugin that replaces the native graph view with a structured, directional graph. Zsolt (the plugin's creator, per the video description's "Support the plugin" link and the first-person build comments) demos it with a guest, Andy, who is a user. The auto-captions render the plugin as "Hlex", "Cape", "Capelex", "caplex" and "Klex", and Excalidraw as "Xcolid" and "Excalibur"; every quote below keeps that spelling. - **The claim.** A graph where directions carry meaning (parents north, children south, friends west, challengers east, with previous and next as a second axis) is a better way to navigate and build a vault than the native graph, which Andy calls cluttered and not that useful once the novelty fades. - **The features shown.** Center-node layout with five areas (parents, friends, challengers, children, siblings), zen mode, an embedded markdown or Excalidraw editor plus a sidecar editor, cross-links and sub-tree expansion, folders, tags and external URLs as nodes, gate counts, live search with keyboard-only navigation, drag-to-create nodes, placeholder nodes, pinning, inline ontologies in parentheses versus YAML properties, inferred versus declared links, expansion of a focused note by its markdown headers, an ontology editor with trigger words, and per-tag node styling. - **Why it matters.** The header-level view (42:30 onward) suggests one long note can expose its internal link structure, which questions the habit of splitting every topic into a separate atomic note. - **Key stakeholders.** Zsolt (builder and channel owner), Andy (guest and user), Obsidian users who rely on graph navigation, and the Sketch Your Mind community, which sells courses and hosts the plugin's discussion. - **Commercial interest.** This is the creator's own product, presented by the creator. The description links a Ko-fi tip jar, a paid Visual Thinking Workshop sign-up, an Obsidian-Excalidraw course and a newsletter, and the closing (00:55:11) mentions a cohort. The transcript never states a plugin price. Andy's praise comes from a community participant, not an independent reviewer. - **Risks and tradeoffs.** The plugin is 3 weeks old (00:04:27). Zsolt names at least four rough edges live: window buttons overlap in full screen, a hotkey clashes with arrow navigation, unlinking an inline ontology is manual, and the filter matches folder paths in a way Zsolt had not expected. Nothing is benchmarked on a large vault. - **Bottom line.** A thorough feature tour with candid bug disclosure and no performance, scale, or accessibility evidence. Worth a trial install on a copy of a vault; treat "beyond awesome" as an enthusiast's opinion. ## 📖 Main content **The core argument.** The native graph shows connections without meaning. K-Plex orients the vault around one focus note and sorts its neighbors into labeled zones. The zones come from the "Idea Compass", a model Zsolt describes at 00:06:38: origins to the north, where an idea leads to the south, similar supporting ideas to the west, transforming or challenging ideas to the east. Previous and next sit on the same left and right edges as a second role pair. Zsolt says this idea predates the plugin, in an earlier Excalidraw-based tool the captions call "Xcoly Brain". **The interface.** The center node is a real vault file. Clicking it opens the markdown note; a button toggles an embedded editor in the center, or a sidecar pane beside the graph. If the file is an Excalidraw drawing, the drawing renders and edits in place (00:06:38). Areas around the center scroll and can be resized by dragging. Any area with a scroll bar gets a quick filter (00:11:48). Settings control how many parents and children show, font size, node width, and text wrapping (00:32:33 to 00:34:00). **Navigation without clutter.** Siblings, cross-links, and child expansion are toggles. Zsolt shows all three on (a busy view) and then all off (a quiet one) and says the busy view is "beyond what's useful" for a note with this many links but could help with fewer items. Gates, the small dots on each node, show whether a node has further connections and carry an exact count (00:18:21). **Folders, tags, and URLs as nodes.** Folders and tags are navigable nodes. K-Plex also indexes every HTTP link in the vault and groups links from one site under a parent domain node. Andy's use case: collect links in a topic note while researching, then later check whether a source already appears somewhere (00:16:08). Zsolt describes an earlier case where a recorded link surfaced a connection nobody expected. **Creating structure from the graph.** You drag a node into an area, choose which ontology applies, and K-Plex writes the relationship into the note. A placeholder node exists only as a reference in metadata or text, shows its referrers, and converts to a real note or Excalidraw drawing on double-click (00:27:19). Dragging from one node's gate to another prompts for a relationship type. Pinned notes and files from the file explorer accept the same drops, which Andy frames as a way to build a map of content. **Two ways to write relationships.** Relationships can live in document properties (YAML) or inline, in parentheses next to a link, such as an ontology term before the link. Zsolt prefers inline because of a writing style built around "data in context text", and says Obsidian Bases only works with document properties. Dotted lines mean the plugin inferred a child relationship because one note simply references another; a right-click lets you reassign it to a declared type. **Header-level analytics.** Expanding a focused note by markdown headers moves each link from the top level into the section where it appears. Links that come from document properties or from other notes stay at the root. Andy says this makes them question whether every topic needs its own note. **Ontology and styling.** The ontology editor holds lists of terms under each category. A suggester with trigger words (double colon plus a letter) filters terms by category, which matters because Zsolt's own ontology has "100 or 100 plus items". Node styles key off tags and overlay (border color, background, icon). Link styles cover dashing, width, label color, and whether the ontology label shows. **Contested or unverified in this source.** There are no numbers on vault size, load time, or battery cost. "Works on my phone" (00:08:50) comes with Zsolt's own caveat that the embedded editor is weaker on a phone. The price, license, and maintenance plan are not stated. The community plugin install path is shown on screen at the close. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=0) Introduction: the missing piece in Obsidian - Andy opens by endorsing K-Plex as something sought "for like several years." Zsolt frames the pitch as a structured graph where directions have meaning. - Zsolt says the plugin has accumulated so many features that Zsolt no longer remembers them all, so the video doubles as a feature inventory. > [!quote] [00:00:00] > This is something I've been looking for for like several years. #### ⏱️ [00:01:08](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=68) The problem with the native Obsidian graph - Andy's complaint: backlinks plus the native graph look attractive at first but end up not useful because of clutter. - The alternative: define ontologies, call up an expected layout, and add to it dynamically. - Zsolt says going back to plain Obsidian is hard now. > [!quote] [00:00:44] > this is the graph that we've always been looking for #### ⏱️ [00:02:11](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=131) Demo vault setup and basic UI - The demo vault was generated with ChatGPT (captions: "Chad GPT") as help material for the plugin, then extended with images by Zsolt. - The center node is an actual markdown file; clicking a side node opens it, and a button opens it in the center instead. > [!quote] [00:02:12] > I asked Chad GPT to generate a demo obsidian vault to as a help for caplex and this is what it came up with. #### ⏱️ [00:03:13](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=193) Zen mode and immersive full-screen view - A new zen mode hides pins, the top search, and the bottom history. A second control makes the graph full screen inside the Obsidian window. - Editing in place uses the normal markdown editor, which can also go full screen. - Live bug: the window maximize and minimize buttons sit on top of the editor in full screen, so Zsolt skips that mode. > [!quote] [00:04:27] > This plug-in is now 3 weeks old. #### ⏱️ [00:04:46](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=286) Understanding the layout: parents, friends, children - The demo note has 12 parents, shown in a scrollable area that can be enlarged. - Parents are origins, friends are lateral ideas, children are where it leads. Clicking a link in the note or a node in the graph recenters the layout. - The right and left edges each hold two roles: friend and challenger, and previous and next. > [!quote] [00:05:11] > parents are the origins of the idea. The note in the center is the note in my focus. Friends are lateral ideas and then there are children. #### ⏱️ [00:06:40](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=400) The Idea Compass and Excalidraw integration - The center note here is an Excalidraw drawing of the Idea Compass, editable in place and switchable back to preview. - North is origins, south is where the idea leads, west is similar supporting ideas, east is transforming challenging ideas. > [!quote] [00:06:38] > you have the origins to the north. You have where the idea leads to to the south. > [!quote] [00:07:22] > supporting ideas to the west and to the east you have transforming challenging ideas. #### ⏱️ [00:08:34](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=514) Adapting the UI: multi-monitor, mobile, sidecar - Andy runs a 49 inch ultrawide at home and a laptop screen on the road, and uses show and hide options to fit each. - Zsolt says the layout works on a phone with the side panel, but the embedded editor is weaker there than the sidecar. > [!quote] [00:08:50] > I think for many use cases actually the sidec car is the the better editor like this somehow. #### ⏱️ [00:09:20](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=560) Opening notes without losing context - Right-click offers open in an adjacent pane, open here, or pop out into a separate window, and several notes can stay open at once. - Andy says this is a recent enhancement and uses it constantly. > [!quote] [00:09:31] > view that note and investigate it without navigating away from the current graph that you're working on. #### ⏱️ [00:10:10](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=610) Graph filtering, lenses, and siblings - A filter panel works like Obsidian Bases lenses: filter, color, and style by criteria, with a code mode that follows graph logic. - Siblings are more distant relations. They can be switched on, resized by dragging, and quick-filtered by typing. - Andy asks what the filter matches; the first answer is the immediate file name. > [!quote] [00:10:19] > you can use lens to filter as well as to color and style items based on predefined criteria > [!quote] [00:11:48] > this filter only looks at the immediate file name #### ⏱️ [00:12:20](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=740) Cross-links and sub-tree expansion - Cross-links show connections among the visible neighbors. Expanding sub-trees shows each node's children. - Zsolt calls the all-on view past the point of usefulness for this note, and recommends turning the toggles off for a quiet view. > [!quote] [00:13:16] > you can just simply turn all of these off and then you get a much quieter view. #### ⏱️ [00:13:40](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=820) Folders and tags as first-class citizens - Folders and tags are navigable nodes. Zsolt defends folders as a time-tested method and notes that Obsidian's core Files plugin already works as a map of contents. - Zsolt admits to many orphan notes because they sit in a known folder, which is a deliberate trade. > [!quote] [00:14:43] > I confess I have lots of notes which are orphan notes because they sit in a folder. #### ⏱️ [00:15:33](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=933) External URL indexing and source research - K-Plex indexes HTTP links across every file. Opening a URL node shows the browser and lists which notes reference it. - Andy's workflow: drop links in a topic note while researching, then check later whether a source already has notes. - Adding a second link on the same site shows that K-Plex groups them under the parent domain node. > [!quote] [00:16:08] > I'll just create a topic note and I'll copy and drop links in there as you know just kind of browsing collecting > [!quote] [00:16:55] > through the link I found a connection that I never thought was there. #### ⏱️ [00:18:55](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1135) Connection gates and reference counts - Gates are the small dots on each node: empty means no children, full means children or connections, and the number says how busy the node is. - Andy compares it to node size in the native graph. Zsolt's answer is that nodes here stay the same size and show exact numbers instead. > [!quote] [00:19:07] > has children or connections. And the number there tells you how busy that connection is. #### ⏱️ [00:20:00](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1200) Live search and keyboard-only navigation - The filter matches the folder path, not the alias, which is why "customize" selected a note in a folder named "filter and focus". Zsolt expects to refine it. - The top search highlights matches or filters the graph to them, with a toggle to include folder paths. - Arrow keys and alt-arrow keys move between areas, Enter recenters, and control-Enter opens the sidecar to edit. > [!quote] [00:20:34] > it's not the alias but it's the folder path that um is captured here. > [!quote] [00:22:04] > I've been paying attention to making sure that you can navigate the entire graph only by keyboard. #### ⏱️ [00:23:40](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1420) Quick node creation and ontological drag-and-drop - Dragging a node into an area assigns a role (the demo makes one a challenger and another a "supercharging idea"). A new node or a placeholder can be created in a click and edited at once. - Andy sees it as a step past mind map scripts in Excalidraw, because here the actual notes and vault structure change. > [!quote] [00:25:04] > you know here you can actually create the notes and manipulate the structure of your vault. #### ⏱️ [00:25:40](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1540) Placeholder nodes: linking ideas before writing - Command or control plus the down arrow adds a next child; a placeholder writes the relationship into the center note's document properties without creating a file. - Typing the same placeholder name into a second note makes K-Plex show it with two referrers and a distinct format. - Double-click converts it to an Excalidraw drawing or a normal note. Zsolt has not added a Canvas option because Zsolt never uses Canvas. > [!quote] [00:25:48] > it only exists in the metadata for this node. > [!quote] [00:26:34] > you have a placeholder with two links to it. #### ⏱️ [00:28:00](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1680) Linking from history and document properties - Dragging from a history node to the center creates a link, and the YAML shows the link under the matching ontology. - Dragging from a different gate prompts for a friend type; the demo vault has related and previous, and choosing previous writes it to that field. > [!quote] [00:28:04] > when I created that link, then the child under the child uh ontology the link was added to document properties. #### ⏱️ [00:29:28](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1768) Pinning nodes for map-of-content building - Pinned notes work like bookmarks and accept the same drag-to-link gestures. - The workflow Andy and Zsolt describe: pin the note being built, browse the graph, link each find to the pinned note, and finish with a populated map of content. > [!quote] [00:29:33] > the pin notes are like your bookmarks. > [!quote] [00:30:18] > And by the end of your discovery, you have all of those things spin, which I think is amazing. #### ⏱️ [00:30:35](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1835) Dragging assets from the file explorer - Dropping an image from the file explorer links it as a parent or challenger. It seems to vanish, and the cause is an attachments toggle that was switched off before the demo, not a bug. - Zsolt tallies two bugs spotted during the session, then retracts this one. > [!quote] [00:31:03] > here I can actually link from the file explorer as well. #### ⏱️ [00:32:00](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1920) Sneak peek: the Wander feature - A planned wander mode makes K-Plex move randomly from node to node, as a discovery tool and a reminder of thousands of notes. - Zsolt hopes to ship a release the captions render as "011" that night, with Wander later. > [!quote] [00:31:50] > So the wandering feature is going to be just simply letting Klex randomly navigate your vault. #### ⏱️ [00:32:51](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=1971) Layout spacing, font sizing, and node width - Controls cover data density, one to three parents, number of children, font size, node width, and text wrapping (wrapped nodes are bigger but fully visible). - Area settings highlight the five zones and set their height. Dragging zones to new positions is planned, low priority. - Compact settings are pitched for mobile. > [!quote] [00:32:33] > You can change the number of parents to show to one, two, or three. #### ⏱️ [00:34:10](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2050) Command palette and Obsidian global hotkeys - Every action publishes to an internal action engine; a subset can be exposed to Obsidian's command palette and bound to hotkeys. - Add child to the center node versus add child to the selected node are separate commands. - Zsolt hits a live conflict: control plus arrow is already used for moving up and down, so the default hotkey is a bug. > [!quote] [00:34:00] > actions are published to this action engine and then I can standardize how they are published. > [!quote] [00:35:28] > you can immediately drop it into your caplex without even having to have caplex active. #### ⏱️ [00:36:10](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2170) Inline ontologies versus YAML frontmatter - Hotkey-added children always go into front matter. Zsolt dislikes that Obsidian Bases only reads document properties. - Inline, a typed term in parentheses before a link sets where that link appears. A bad term still resolved because "explains" is a child relation. - Andy asks which style Zsolt recommends; the answer is taste. > [!quote] [00:36:11] > something that I don't like in Obsidian bases that it only works with document properties. > [!quote] [00:37:37] > I can add ontology right in here as I'm typing. #### ⏱️ [00:38:40](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2320) Inferred links versus explicit semantic relationships - A dotted line marks an inferred child relationship. Right-click lets you change "similar to" to a friend on the left. - Unlinking is weak: the ontology term lives in the sentence, so you must go to source and edit by hand. Zsolt admits to being "at two minds" and wants a one-click unlink. - Hovering a link shows its source definition and connection details, which matters when several references push a note into an unexpected area. > [!quote] [00:38:24] > The dotted line means it's an inferred relationship. > [!quote] [00:39:51] > I'm not very friendly with with having document properties at the top > [!quote] [00:40:36] > So it should be easy to unlink. > [!quote] [00:42:02] > you can actually read the connection details and and you can see the evidence behind why all of this here #### ⏱️ [00:42:30](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2550) Deep analytics: expanding a focused note by headers - Andy reports that inline definitions plus header expansion may change their note-taking. - The demo note gets a top-level child, section one, and section two. Pressing the header toggle moves each link into the section that holds it. - Links from document properties or from other notes remain at the root. Sections can be expanded one at a time or broken down further. > [!quote] [00:42:47] > do I need to create all of these separate notes, right? > [!quote] [00:42:47] > Making it making it atomic. It's just not a separate note. > [!quote] [00:44:11] > So the links from up there suddenly moved down here into the section. > [!quote] [00:44:57] > this gives you this analytic of how your note is structured from a linking perspective #### ⏱️ [00:47:29](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2849) Customizing ontologies, categories, and trigger words - Plugin settings cover navigation speed, fit to page, node label length, and display of alias or custom fields. - A new feature in the coming release treats a date property as a link to the daily note and lets you choose which area inferred date links use. - The suggester filters terms by category after a double colon and a letter. Zsolt's own ontology has more than 100 terms. - Andy notes inline use avoids template-stamped empty YAML fields on notes where they make no sense. > [!quote] [00:46:24] > if you have a date field in document properties, it's automatically going to be interpreted as a link to > [!quote] [00:47:50] > if I come here and press double colon F then I only get the friend ontologies. > [!quote] [00:48:33] > a bunch of empty empty fields on the top #### ⏱️ [00:49:25](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=2965) Visual styling: custom tags, icons, colors, link types - A discovered-fields list shows frontmatter keys with no ontology assigned yet. - Display name uses an ordered list of fields (alias first, then title, and so on). - Node styles come from a privileged tag (document, project memo, person, book) plus stackable tag styles for border, background, and icon. - Link styles cover dashed or solid lines, width, label color, and whether the ontology label displays. > [!quote] [00:49:18] > you can actually have multiple fields and these are in order of priority. > [!quote] [00:50:47] > you can overlay multiple tags #### ⏱️ [00:52:15](https://www.youtube.com/watch?v=XIq8uf8OaNI&t=3135) Closing thoughts and how to install - Andy's pitch: it works the way you think, and the creator answers community questions fast. A community comment Andy cites calls it a main navigation method. - Zsolt shows the install path: Obsidian community plugins, browse, search for the plugin name. No Excalidraw or Dataview needed. - Zsolt credits the 3-week build to agentic development alongside a day job, the Excalidraw plugin, a community, and a cohort, and asks for GitHub issues and feature requests. - Zsolt says the task-management ideas list has no visible end. > [!quote] [00:52:16] > it's intuitive, right? It's it works naturally how you think and how you want to develop things. > [!quote] [00:52:59] > this is going to be you know my main navigation method when using Obsidian. > [!quote] [00:54:28] > You can install Caplex from here. You need nothing else. > [!quote] [00:55:11] > This is the magic of agentic development that we can achieve this much progress myself next to a day job > [!quote] [00:55:55] > I don't yet see the end of the list ## 📚 References The transcript itself contains no links; the following come from the video description or are primary sources for named entities. - [Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo](https://www.youtube.com/watch?v=XIq8uf8OaNI): the source video, 56:08, uploaded 2026-10-10. - [K-Plex on GitHub](https://github.com/zsviczian/kplex): plugin source and issue tracker, from the description. Zsolt asks viewers to file issues and feature requests here (00:55:11). - [K-Plex demo vault](https://github.com/zsviczian/kplex-help): the help vault shown in the demo, from the description. The transcript says it was generated with ChatGPT and extended by hand. - [K-Plex v0.0.4 announcement thread](https://community.sketch-your-mind.com/t/k-plex-v0-0-4-a-major-leap/11153): Sketch Your Mind Community post, from the description. - [Obsidian](https://obsidian.md): the host application; K-Plex installs from its community plugins browser (00:54:28). - [Sketch Your Mind Community](https://community.sketch-your-mind.com/welcome): Zsolt's community, where the guest and host met (00:54:28). The description also lists the Visual Thinking Workshop, an Obsidian-Excalidraw course, and a newsletter, which are the creator's commercial offerings. - [Ko-fi: support the plugin](https://ko-fi.com/zsolt): tip jar from the description. - Obsidian Bases: core plugin Zsolt compares against (00:10:19, 00:36:11). No URL is given in the transcript; use Obsidian's official docs. - Excalidraw plugin for Obsidian: the drawing editor embedded in the center node. The captions render it "Xcolid" and "Excalibur". ## 🗣️ Paraphrase Zsolt built an Obsidian plugin that puts one note in the middle of the screen and sorts its neighbors by meaning: where the idea came from above it, where it leads below it, similar ideas to the left, challenging ideas to the right. Andy, a user, says this beats the native graph because the native graph piles up lines without telling you what they mean. The demo moves from reading to writing. You can click through the vault, edit the center note in place, then drag one node onto another to create a typed link, which the plugin writes into your note either as a YAML property or as an inline term in parentheses. You can create placeholder notes that exist only as references until you decide to write them, pin a note you're building as a map of content, and expand a long note by its headers to see which section holds which link. Zsolt shows bugs as they surface, says the plugin is 3 weeks old, and credits AI-assisted development for the pace. The video ends with the install path and a request for GitHub issues. ## 📰 Newsletter **A graph that tells you which way is up.** Obsidian's native graph shows everything connected to everything. K-Plex, a community plugin from Zsolt of Sketch Your Mind, shows one note in the center and sorts its neighbors into parents, children, friends, and challengers. In a 56-minute walkthrough with a user named Andy, Zsolt shows you can drag nodes to create typed links, keep placeholder notes before writing them, and expand one long note by its headers to see where each link lives. Two things stand out for people who write and document in Obsidian. First, the inline syntax: a term in parentheses before a link sets its relationship, so you don't need YAML on every note. Second, the header expansion, which Andy says may reduce how many separate atomic notes they create. Tone check: this is the creator demoing their own plugin, 3 weeks old, with bugs shown on screen. It's a good feature tour and a poor benchmark. Try it on a copy of your vault. Links: [the video](https://www.youtube.com/watch?v=XIq8uf8OaNI), [K-Plex on GitHub](https://github.com/zsviczian/kplex), [Obsidian](https://obsidian.md). ## ✅ Action items #### DevRel - Developer advocacy: run a 20-minute live trial of K-Plex on a copy of a docs vault and publish what worked and what broke, with the plugin version stated. - Education: add "typed links versus plain links" to a PKM or documentation office hours session, using the Idea Compass as the example. - Developer experience: if the team keeps docs notes in Obsidian, test whether the inline ontology syntax or YAML properties survive a Markdown export without losing relationships. - Developer marketing: when quoting this video, state that the presenter built the plugin and sells related courses. Don't present Andy's praise as independent. - Community management: no direct action from this source; nearest relevance: the video shows a creator answering feedback in a community and on GitHub, a pattern worth copying. - Internal/external: check the K-Plex GitHub issue tracker before recommending it, and file the unlink and hotkey issues if they're still open. #### OSPO - Policy and governance: decide whether community Obsidian plugins are allowed on machines that hold work notes, and write the rule down. - License compliance: read the repository license before any team adopts or forks the plugin. The transcript doesn't state one. - Security management: a plugin that indexes every URL and reads all vault files has full vault access. Review its network behavior and permissions before use on sensitive notes. - Software inventory: a plugin built over 3 weeks by one maintainer is a single-maintainer dependency. Record its version and last release date if anyone relies on it. - Developer support: no direct action from this source; nearest relevance: a short "how we trial a new plugin" checklist. - Community engagement: no direct action from this source; nearest relevance: Zsolt invites GitHub issues and community hours. - Strategic alignment: no direct action from this source; nearest relevance: the AI-assisted build pace (00:55:11) is a data point for maintainer-capacity discussions. #### Community - Maintainers: no direct action from this source; nearest relevance: Zsolt names the plugin's own bugs live, which models honest status reporting. - Contributors: no direct action from this source; nearest relevance: GitHub is the stated path for issues and feature requests. - Sponsors: no direct action from this source; nearest relevance: the description's Ko-fi link is the only sponsorship path named. - Ecosystem: no direct action from this source; nearest relevance: K-Plex depends on Obsidian and optionally Excalidraw, so Obsidian API changes are the ecosystem risk to watch. #### WordPress - Core: no direct action from this source; nearest relevance: none. - Core Performance: no direct action from this source; nearest relevance: none. No performance data appears. - Core AI: no direct action from this source; nearest relevance: a 3-week AI-assisted plugin build is a case study for AI-assisted contribution policy. - **Core Program Team:** no direct action from this source; nearest relevance: none. - Mobile: no direct action from this source; nearest relevance: Zsolt says the layout works on a phone but the embedded editor is weaker there (00:08:50). - Playground: no direct action from this source; nearest relevance: none. Obsidian plugins don't run in Playground. - Community: no direct action from this source; nearest relevance: a contributor-handbook "personal knowledge tools" page could mention typed links. - Training: no direct action from this source; nearest relevance: the Idea Compass is a usable teaching device for concept mapping in a lesson plan. - Marketing: no direct action from this source; nearest relevance: none. - Support: no direct action from this source; nearest relevance: none. - Design: no direct action from this source; nearest relevance: node styles keyed to tags (border, background, icon) are a reference for visual taxonomy. - Documentation: test whether a handbook page's link structure looks sensible when expanded by headers, as in the 42:30 demo. It's a cheap way to spot a page that should be split. - Photos: no direct action from this source; nearest relevance: none. - TV: no direct action from this source; nearest relevance: none. - Polyglots: no direct action from this source; nearest relevance: none. The interface is English only in this demo. - Accessibility: no direct action from this source; nearest relevance: see the accessibility section. Test the plugin's keyboard navigation and screen reader output before recommending it. - Meta: no direct action from this source; nearest relevance: none. - CLI: no direct action from this source; nearest relevance: none. - Hosting: no direct action from this source; nearest relevance: none. - Tide: no direct action from this source; nearest relevance: none. - Openverse: no direct action from this source; nearest relevance: none. - Themes: no direct action from this source; nearest relevance: none. - Plugins: no direct action from this source; nearest relevance: none. #### The WPOCC - Programs: no direct action from this source; nearest relevance: none. - Projects: no direct action from this source; nearest relevance: a plain note-linking convention for governance documents could borrow the parent, child, friend, challenger vocabulary. - Funding experiments: no direct action from this source; nearest relevance: single-maintainer tools funded by tips and course sales are the model The WP Open Community Collective would be comparing against. ### FAIR - Technical independence: K-Plex stores relationships as plain Markdown and YAML in local files, which is portable. Verify that claim by opening a relationship-heavy note in a plain editor. - Policies and covenants: no direct action from this source; nearest relevance: none. - Productized governance artifacts: no direct action from this source; nearest relevance: none. ## 🧪 Hypotheses 1. Expanding a focused note by headers reveals at least one section per long note that links to topics unrelated to the rest of the note, which marks a split candidate. 2. For users who keep relationships inline, the number of empty YAML property lines per note drops to near zero versus a template-stamped properties approach. 3. On a vault of 10,000 or more notes, the center-node layout stays interactive (under 1 second to recenter) because it renders one note's neighborhood, not the whole graph. 4. Users who adopt keyboard-only navigation recenter on a target note faster than users clicking through the native graph. 5. Inferred (dotted) relationships mislead users about intended meaning in more than 10% of cases once a note has several references. 6. The plugin's rough edges named in the demo (full-screen button overlap, hotkey clash, manual unlink) are fixed within two releases, given the maintainer's stated release pace. ## 📊 Methodology - **Design for H1.** Take 30 notes of 1,500 or more words from a real vault. Expand each by headers and count sections whose links share no topic with sibling sections. Two reviewers label each and report agreement. - **Design for H2.** Compare two copies of the same 200-note vault: one using YAML templates, one using inline ontologies. Count empty or unused property lines and total frontmatter lines. - **Design for H3.** Generate synthetic vaults at 1,000, 10,000, and 50,000 notes with a fixed link density. Time recenter and search from three cold starts each, on a stated machine and Obsidian version. - **Design for H4.** A within-subject task: find and open 20 named notes using the native graph, then K-Plex keyboard mode. Record time and errors. Counterbalance the order. - **Design for H5.** Sample 100 dotted-line links from a real vault and ask the note's author whether the inferred role matches intent. - **Design for H6.** Track release notes on the GitHub repository for the three named issues across the next two releases. - **Controls throughout.** Same vault copy, same Obsidian version, plugin version recorded, and a fresh vault for each arm. ## ❓ Questions - What does the plugin cost, what license does it use, and what is the long-term maintenance plan for a project one person built in 3 weeks? - How does it behave on a vault with tens of thousands of notes, and on mobile hardware? - What exactly does the filter match: file name, alias, folder path, or all three? The answer changes during the demo (00:11:48 versus 00:20:34). - How do inline ontology terms interact with other plugins that parse links, such as Bases, Dataview, or publish tooling? - What happens to relationships if the plugin is removed? Are inline terms in parentheses readable as plain text? - Can an inferred relationship be promoted to a declared one in one click, and demoted back? - Is the plugin usable with a screen reader and keyboard only, beyond the arrow-key navigation shown? - How does the date-to-daily-note feature handle several date fields on one note? ## 🔮 Future research - **Header-level link analytics as a splitting heuristic.** Zsolt and Andy suggest the view reduces the need for atomic notes. There's no study of whether it improves retrieval or just defers a split. - **Graph navigation versus search and backlinks.** Controlled comparison of task time and recall for finding related notes, across native graph, backlinks, and a structured graph. - **Ontology size and usability.** Zsolt's ontology has 100 or more terms. Research on how many relationship types users can hold in memory, and whether trigger-word filtering fixes the problem. - **Inferred versus declared links.** How often does an inferred child relationship match what the author meant? - **Single-maintainer plugin sustainability.** How long do rapidly built, AI-assisted plugins stay maintained after the first few weeks? ## 💡 Implications - **Practice.** Typed relationships written inline, next to the sentence that justifies them, keep evidence beside the link. The hover panel (00:42:02) shows the source of each link, which turns the graph into an audit view. - **Policy.** A plugin with full vault read access that was 3 weeks old at recording needs a review step before it touches work notes. The demo shows what the plugin can see: every URL, every folder, every tag. - **Security.** URL indexing means every link in a vault is collected into one view. Notes with private links, tokens in URLs, or customer data should be excluded or reviewed first. - **Education.** The Idea Compass is a compact vocabulary for teaching how ideas relate: origin, consequence, support, challenge. It works without the plugin. - **Funding.** The commercial context (tips, workshop, courses, cohort) shows how a free-to-install plugin is sustained. Whether that supports long-term maintenance is not shown. - **Vendor literacy.** A demo hosted by the builder with a friendly guest is a product tour. The honest bug disclosure raises its credibility without replacing independent testing. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level on the auto-transcript is about 6 and Flesch Reading Ease about 80, computed with a rough syllable heuristic on 8,246 words. Auto-caption sentence breaks are unreliable, so treat both as approximate. The vocabulary is plain, but terms such as ontology, document properties, MOC, and sidecar assume an intermediate Obsidian user. #### 👀 Visual learners - Present: the entire video is a screen recording of the graph, with live drag-and-drop, color, dotted lines, and the Idea Compass drawing. - Improve: no diagram summarizes the five areas and two role axes. A single labeled compass graphic at 04:46 would anchor the rest. Narrate colors and icons for viewers who can't see them. #### 🔊 Aural learners - Present: two speakers talk throughout, so the video works as a conversation. - Improve: much of the explanation points at the screen ("here", "this", "right there"). A voice-only summary of the zones and the gate symbol would stand alone. #### 🗣️ Verbal learners - Present: terms such as gates, friends, challengers, and placeholder are defined as they appear, and the compass directions are stated. - Improve: ontology, MOC, and sidecar go unexplained for newcomers. A written glossary in the description would help. #### 🧩 Kinesthetic learners - Present: the demo vault is public on GitHub, so a viewer can install the plugin and repeat each step. - Improve: no numbered exercise list. A "try this in 10 minutes" checklist (drag a node, make a placeholder, expand by headers) would convert watching into doing. #### 🧠 Logical learners - Present: Zsolt separates declared from inferred links and explains the rule for dotted lines (00:38:24). The root versus section distinction in header expansion is explained. - Improve: no rules table for when a link lands in which area. The "why is this here" question comes up at 00:42:02 and is answered only by a hover panel. #### 🧑‍🤝‍🧑 Social learners - Present: two voices, a live Q&A feel, and repeated pointers to the community and GitHub. - Improve: no discussion prompts. Pose a question such as "inline or YAML, which do you use?" in the description to seed the comments. #### 🧘‍♀️ Solitary learners - Present: the 28 chapters let a solo viewer jump to a feature and replay it. - Improve: no self-check. A short list of "after this chapter you should be able to..." items would help. #### 🌿 Naturalistic learners - Present: the compass, with its north and south directions, is a spatial metaphor, and "wander" mode offers a walk through the vault. - Improve: nothing in the source ties the tool to natural systems. The wander feature could be framed as foraging, but that's the viewer's inference, not the video's. ## 📊 Accessibility assessment #### Screen reader semantics - Present: the YouTube player supplies standard landmarks and controls, and the description is plain text with labeled links and chapters. - Improve: the video conveys the graph visually. Whether K-Plex exposes roles, names, and relationships to assistive technology is not shown or said. WCAG 2.2 AA 1.1.1 (Non-text Content) and 4.1.2 (Name, Role, Value) apply to the plugin and are untested here. Audio description (1.2.5) is absent for on-screen actions. #### Keyboard navigation - Present: Zsolt demonstrates keyboard-only navigation with arrow keys, alt-arrow keys, Enter, control-Enter, and hotkeys for commands (00:22:04 to 00:23:35). - Improve: Zsolt shows a conflict where control plus arrow clashes with the plugin's own navigation (00:35:28). 2.1.1 (Keyboard) is partially evidenced; 2.1.2 (No Keyboard Trap) and 2.4.7 (Focus Visible) are not shown. Drag-and-drop creation is the headline feature; 2.5.7 (Dragging Movements) requires a non-drag alternative, and the keyboard add-child commands may serve as one. #### Contrast and readability - Present: unverifiable from a transcript. The video's colors are chosen by the user, with per-tag border, background, and icon styles. - Improve: because color styling is a main feature, 1.4.1 (Use of Color) and 1.4.11 (Non-text Contrast) matter for dotted versus solid lines and node borders. Zsolt asks viewers twice whether the dotted line is visible enough (00:38:24), which hints at the problem on video. #### Text resizing and reflow - Present: the plugin has a font size setting and a text-wrap toggle that makes nodes wider so text stays visible (00:33:16). - Improve: Zsolt says the settings pane "doesn't resize" at 00:45:40. Against 1.4.4 (Resize Text) and 1.4.10 (Reflow), that's a stated gap. Burned-in video text does not scale. #### Media and captions - Present: chapters exist (28 in the metadata), and an auto-generated transcript exists. - Improve: the captions garble the plugin name six or more ways (Hlex, Cape, Capelex, caplex, Klex, Apex) and Excalidraw as "Xcolid", "Xcoly", "Excalibur". That's a 1.2.2 (Captions, Prerecorded) failure in substance. Human-corrected captions would fix it. #### Forms and interactions - Present: no forms in the video. The plugin's settings use toggles, drop-downs, and text fields that are shown but not described. - Improve: label and error behavior is untested (3.3.2 Labels or Instructions). Right-click menus (unlink, change ontology) need a keyboard path (2.1.1). #### Standards reference - Primary gaps against WCAG 2.2 AA, as inferred from the published video: **1.2.2** (inaccurate captions), **1.2.5** (no audio description for on-screen actions), **1.4.1 / 1.4.11** (color-dependent graph styling, not shown to be accessible), **2.5.7** (drag as the core interaction), **1.4.4 / 1.4.10** (settings pane doesn't resize). These apply to the video as published and to claims about the plugin that the video does not test. ## 🌍 DEIB assessment #### Cultural breadth - Present: the examples are English-language notes in a demo vault, with a community that spans countries (the description lists Discord, Mastodon, and Twitter handles). - Improve: the demo uses no non-English notes or right-to-left text. Showing how ontology terms, aliases, and trigger words behave in another language would test the claim of a universal tool. #### Inclusive language - Present: the language is direct and plain. The compass uses neutral directional terms. - Improve: "I know I'm not your average Joe" (00:39:51) is an idiom; plain wording would travel better. "Challengers" and "friends" are metaphors that a glossary would define. #### Neurodiversity support - Present: 28 chapters and a consistent structure (concept, demo, caveat) make the video navigable. The tool itself offers a quiet mode, with every clutter toggle switchable off. - Improve: the conversation drifts, and Zsolt says "we are now a bit off track" at 00:14:43. Fast pointing at the screen ("here", "this") is hard to follow without visual references. Zen mode and quiet mode are a strength worth stating as such. #### Representation - Present: two speakers, a creator and a user. Andy represents the non-builder audience. - Improve: no independent reviewer, critic, or user with a different workflow (accessibility needs, a non-English vault, a large corporate vault) appears. #### Psychological safety - Present: both speakers are warm, and Zsolt admits mistakes, retracts a bug claim at 00:31:03, and invites issues. - Improve: superlatives ("beyond awesome", "magic") can make a viewer who struggles with the tool feel the fault is theirs. Pair them with the stated limits, such as the 3-week age. ## ✅ Logical validity #### Strong reasoning - **Demonstration, 00:11:02 to 00:13:16.** Turning siblings, cross-links, and sub-tree expansion on and then off shows the clutter tradeoff directly. Zsolt states where the busy view stops being useful. That's evidence for "you control the density", the narrow claim being made. - **Mechanism, 00:38:24.** The dotted-line rule is stated as a rule: if one node references another, the plugin infers a child relationship. A right-click converts it to a declared type. The rule is explicit and checkable. - **Use-case reasoning, 00:16:08.** Andy's research workflow (collect links now, check for earlier notes later) ties the URL index to a concrete need and a concrete benefit. - **Self-correction, 00:31:03.** Zsolt calls the vanished image a bug, finds the attachments toggle, and retracts the claim. That's honest debugging on camera and raises trust in the rest of the demo. - **Candor about limits, 00:04:27 and 00:35:28.** Naming the plugin's age and live bugs sets expectations. Strengthen it by listing known issues in the description. #### Fallacies - **Appeal to enthusiasm, 00:00:00 and 00:53:43.** "this is so super superior that to me it's it's just uh it's just magic." Strong feeling stands where evidence of improvement would go. *Fix:* state a measurable gain, such as time to find a related note. - **Anecdote as evidence, 00:52:59.** A community comment that this will be "my main navigation method" is offered as support. It shows adoption intent, not benefit. *Fix:* report usage after 3 months, not first impressions. - **Undisclosed or understated interest (commercial), 00:00:44 to 00:55:55.** The creator presents their own plugin, the guest is a community member, and the description sells workshops and courses. The video never states the relationship as a disclosure. *Fix:* a one-line "I built this plugin and run a paid community" at the start. - **False dilemma, 00:14:00.** The framing that folders are looked down on by PKM communities and that folders are time-tested sets up a contrast few people hold. The claim that folders are valid is reasonable; the implied opponent is a straw position. *Fix:* cite the actual objection (folders force a single location) and answer it. - **Hasty generalization, 00:43:28 to 00:45:40.** "you might not even want to create a separate note" is drawn from a three-section toy note. Whether header-level views replace atomic notes for real research notes is untested. *Fix:* demonstrate on a real 3,000-word note. - **Unsupported superiority claim, 00:53:43.** "there's definitely no way going back because this is so super superior" has no comparison. Hyperbole is flagged by Zsolt as "a bit of an overstatement" in the same sentence, which softens it. *Fix:* name what was measured. #### Tone of voice - Warm, fast, and conversational, with two friendly speakers. Contractions and first person throughout. Enthusiasm runs high at the open and close ("awesome", "magic") and drops to practical in the middle, where the demo includes bugs, hesitations, and corrections ("Okay, the hotkey is not ideal"). The pattern: marketing at the edges, engineering in the middle. The middle is where the useful information sits. ## 🛡️ DARVO analysis Not applicable to this source. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response to accusation or criticism, and this is a friendly product demo with no accuser. For completeness across the three prongs: **Deny**: nothing is denied. Bugs are named, and one claimed bug (the vanished image) is retracted at 00:31:03 after a configuration check. **Attack**: no critics or competing tools are attacked. Obsidian Bases is criticized as a design choice (document properties only), a feature comparison, not a personal attack. **Reverse victim and offender**: no such move appears. ## 🎯 Conclusion K-Plex turns Obsidian's graph from a picture of connections into a working surface: one focus note, five areas with fixed meanings, drag-to-link that writes real relationships into your files, placeholders for notes you haven't written, and a header-level view that shows which part of a note holds which link. That mechanism is shown live, and the dotted-line rule at 00:38:24 and the section expansion at 00:44:11 are the clearest evidence. What the source can't support is scale, price, longevity, and accessibility. The plugin is 3 weeks old, has several bugs shown on screen, and was demoed by its creator with a community guest. No benchmark, no license, and no user study appears. The commercial context (courses, workshop, cohort, tips) is listed in the description but never disclosed in the talk. **Next steps for readers:** install the plugin on a copy of a vault with at least a few hundred notes, test header expansion on one real long note, and check the GitHub repository for the license and open issues before relying on it. If you use screen readers or keyboard only, test navigation and drag alternatives before recommending it. ## 🔄 Refactor Appendix — Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 4 Literature, 2 Permanent. Resonance filter applied: the Wander preview and > styling settings were dropped as feature detail without a transferable claim. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Gate counts show connection volume without opening notes > [!quote] [00:19:07] > has children or connections. And the number there tells you how busy that connection is. **Context & use**: - 00:19:07, explaining the dots on each node after Andy compares them to node size in the native graph. - Exact numbers replace the native graph's size cue. Worth keeping as a concrete design contrast. **Tags**: #xref  #### [H2] Header expansion makes sections behave like separate notes > [!quote] [00:42:47] > Making it making it atomic. It's just not a separate note. **Context & use**: - 00:42:47, Andy on how expanding a focused note by headers may change their note-taking. - The demo uses a toy three-section note. Record the claim with the caveat that it hasn't been tried on a long real note. **Tags**: #xref #articleseed  #### [H3] Inline ontologies keep relationships inside the sentence > [!quote] [00:37:37] > I can add ontology right in here as I'm typing. **Context & use**: - 00:37:37, showing a parenthesized term before a link that places it in the graph. - The cost, shown at 00:40:36, is that unlinking means editing the source sentence by hand. **Tags**: #xref  #### [H4] Agentic development compresses a plugin's first weeks > [!quote] [00:55:11] > This is the magic of agentic development that we can achieve this much progress myself next to a day job **Context & use**: - 00:55:11, Zsolt explaining how a 3-week-old plugin has this many features. - The same speed produced the visible rough edges. Pair the claim with the bug list when citing it. **Tags**: #xref #share  ### 🧠 Atomic Split Pad #### [P1] Relationships belong next to the sentence that justifies them **Claim** (one sentence, Courtney's voice): A typed link written inside the sentence that explains it carries its own evidence, while a property at the top of the note carries only the label. **Evidence pointer**: [[#H3]] · [[#H2]] **Scope & conditions**: Holds for prose notes where the surrounding sentence explains the link. Breaks for structured records, such as people or books, where a uniform property schema is the point. Also breaks when you need to remove a link often, since the demo shows unlinking is manual for inline terms. **Links**: - [[Atomic notes]] — because contrasts on whether one idea needs its own file - [[Typed links in Obsidian]] — because extends - [[Obsidian Bases and properties]] — because contrasts on where relationship data lives  #### [P2] A builder's demo shows capability, not fit **Claim** (one sentence, Courtney's voice): A demo by a tool's creator, with a user as host, proves what the tool can do and says little about whether it fits a different vault. **Evidence pointer**: [[#H4]] · [[#H1]] **Scope & conditions**: Applies to any single-creator product tour. Weakens when the demo includes live failures, as this one does at 00:31:03 and 00:35:28, and when an independent test exists. Doesn't apply to the mechanisms shown on screen, which can be verified by installing the plugin. **Links**: - [[Reading vendor claims]] — because extends - [[Self-limiting disclosure raises credibility]] — because evidence-for - [[Plugin trial checklist]] — because applies-in  ### ✏️ Fleeting Queue - [F1] Check the K-Plex repository license and open issues before any recommendation: https://github.com/zsviczian/kplex #fleeting #inbox - [F2] Test header expansion on one real 3,000-word note and record whether any section should have been its own note #fleeting #inbox - [F3] Open question: do inline ontology terms in parentheses stay readable if the plugin is uninstalled? #fleeting #inbox - [F4] Compare the Idea Compass (parents, children, friends, challengers) with my own link vocabulary in the vault #fleeting #inbox - [F5] Article seed: "Marketing at the edges, engineering in the middle" applies to this demo as well, since the live bugs sit in the middle third #fleeting #inbox #articleseed - [F6] Check whether the plugin exposes anything to a screen reader and whether drag-to-link has a keyboard path #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Install K-Plex on a vault copy and try header expansion on one long note: vault experiment, 30 min #things - [ ] Read the K-Plex license and open issues on GitHub before recommending it to anyone: due diligence, 10 min #things  📄 **Full text:** [[Full Document Contents/Articles/Obsidian Graph View Reimagined Full K-Plex Walkthrough & Demo.md|Obsidian Graph View Reimagined: Full K-Plex Walkthrough & Demo by Zsolt's Visual Personal Knowledge Management]] ## Highlights - [00:19:07] has children or connections. And the number there tells you how busy that connection is. So when I look at a node I can immediately see that how how broadly it is referenced even without opening the node which I think gives you immense power in terms of navigating all of this. But I think you >> that's that's kind of a similar thing to the native obsidian graph and the node being bigger the more connections it has. Right. >> Yeah. Exactly. But here here it's not bigger. I [00:19:49] >> the numbers. Yeah. >> Yeah. Here I'm showing exact numbers which >> I think are >> more valuable. >> Well I I think so. Yes. Now on the filter. So you asked. Yes. So this filter is going to filter on the displayed name. So yeah, you can see I started to type customize. H. It might not be looking at the names because I don't see the the word cus in here. It's a very interesting question. Focus. No, it's in the folder name. So you can see there the reason this one is selected is because 04 filter and focus. So it actually filters ([View Highlight](https://read.readwise.io/read/01m4rbb8sh10c8pkvr9wc15rb4)) - Note: [H1] Gate counts show connection volume without opening notes - Tags: atom/literature/h1 - [00:36:55] here I can add explains a supercharging that itself. That's not a clever link. Explains work with web sources and dot dot dot. So that should actually resolve. So that's a very good question there. Oh, explains is a child relation as well. I managed to find a child. So I want to add a a a friend What do you say? Yeah, that's what I wanted to show you. So, within the text, I can add and there you go. It's now a [00:37:37] friend relation up here. But I can add ontology right in here as I'm typing. And so, those are the parentheses here. If you can if you can see that. So, this is in parentheses. And with that, I can denote that within this sentence this link has an ontology. I tell it where it should be displayed in the graph and you can define your own polies. So this is one possible but for example I could also say that this is similar to two and I can choose indexing and problem troubleshooting. I'm just adding a link. ([View Highlight](https://read.readwise.io/read/01m4rbbdjs58505bskg9kys05x)) - Note: [H3] Inline ontologies keep relationships inside the sentence - Tags: atom/literature/h3 - [00:42:47] field and and the value and the link, the ability to expand the focused node by headers and then it showing where that link think resides is making me think, do I need to create all of these separate notes, right? Which I would typically historically do because they're separate topics, but being able to view it with those expanded headers and then where that link resides is, you know, uh atomizing it, right? Making it making it atomic. It's just not a separate note. >> So, >> yeah. So, so, so this is what you're talking about that [00:43:28] >> really cool feature. >> I edited the supercharging idea node and now you can see I have >> add a next child as >> a top level item. It's not part of any of the sections and then I have section one and section two. Maybe I'm going to do it like this just to make it more fun that this is going to be section to one like that. So the remaining links you can imagine long paragraphs with lots of links I broken up like this and and what you see here is you see these links listed uh under this. But if I click ([View Highlight](https://read.readwise.io/read/01m4rbbb3g6gptjntq8yzven67)) - Note: [H2] Header expansion makes sections behave like separate notes - Tags: atom/literature/h2 - [00:54:28] And there you go. You can install Caplex from here. You need nothing else. So you don't need Excel. You don't need data view. Apex in itself is fully self-sufficient. And then if you want to engage then I'm going to include the link below. I encourage you to join the sketch your mind community there. We have some amazing chats about this and I'm sure we're going to have multiple community hours as well when we we talk. I met Andy there as well. So, um, that's where the the connection comes from. As well as, of course, if you have an idea, a [00:55:11] feature request, you run into an issue, record it on GitHub. I'm processing these items. Again, the plug-in is three weeks old. This is the magic of agentic development that we can achieve this much progress myself next to a day job and next to keeping Excalibur going and the community and running my story OS cohort. So lots of other things on the side and still this is all possible that's um amazing but yeah if you find an issue or if you have an idea drop it into GitHub join the community let's have a discussion and let's make this tool even better. I I still have lots of ideas in terms of how to manage tasks ([View Highlight](https://read.readwise.io/read/01m4rbbg1skff73v00ggttn735)) - Note: [H4] Agentic development compresses a plugin's first weeks - Tags: atom/literature/h3