The argument in one line.
Plain markdown notes are excellent for storage and for AI to read but useless for actually seeing the state of a business, and describing the dashboard you want to Claude Code in plain English is now a faster path to a custom visual tool than configuring a generic table view.
Read if. Skip if.
READ IF YOU ARE…
- You keep your business or personal knowledge in a folder of Obsidian or markdown notes and are tired of hunting through folders or staring at a plain table view to find anything.
- You want to build small custom internal tools, like dashboards, trackers, or status boards, but don't know how to code and don't want to touch a terminal.
- You already use Claude Code for programming projects and are curious what else it can build outside of traditional software.
SKIP IF…
- You don't use Obsidian or markdown-based notes — the specific plugin-building steps won't transfer directly.
- You're looking for a finished, downloadable dashboard template rather than a process for building your own.
The full version, fast.
A solo business owner runs everything from a folder of Obsidian markdown notes, but plain files and folders make it hard to see the state of any project, and Obsidian's built-in Bases feature only offers a generic filterable table. Instead of settling for that, she uses Claude Code to build six custom dashboard plugins — one each for her daily agenda, content pipeline, knowledge inbox, projects, and business areas — that render the same notes as visual cards, progress bars, and grouped tabs. The build process needs no coding or terminal knowledge: she describes the dashboard out loud, Claude Code writes the plugin, and she toggles it on inside Obsidian. The prerequisite is consistent frontmatter properties (type, status, area, cycle) on every note, plus picking one visual style upfront so multiple dashboards stay consistent.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 03:42
01 · Intro: the problem with folders and Bases
She explains why plain markdown notes and Obsidian's built-in Bases table view fall short, previews the video's 3-part structure, and pitches her paid College of Knowledge community.
03:42 – 09:17
02 · The Dashboards I Built
Walkthrough of the custom plugins she had Claude Code build: a Projects dashboard, a Content dashboard, and a Daily OS combining calendar, cycle tracking, and agenda.
09:17 – 11:23
03 · Claude Code + Obsidian in Action
How she actually runs Claude Code against her vault, via the Claude desktop app, the VS Code extension, or her own free Hyo Agent Obsidian plugin, without ever touching a terminal.
11:23 – 16:16
04 · Building a Dashboard Live (Demo)
She builds a new 'Areas OS' plugin live by describing it out loud, then iterates in conversation with Claude Code to convert accordion sections into filterable tabs.
16:16 – 20:35
05 · What I Learned Vibe Coding Obsidian Plugins
Lessons on keeping a consistent visual style guide across plugins, and why every note needs consistent frontmatter properties (type, status, area, cycle) before a dashboard can be built on top of it.
Lines worth screenshotting.
- Markdown files are great for storing notes but bad for finding them again — plain folders force you to remember where you put things.
- Obsidian's built-in Bases feature only renders a table view with filters and groupings, which some builders find too limited and visually plain.
- A custom dashboard plugin can show the same underlying data as a table view but as visual metric cards, progress bars, and drag-and-drop status columns.
- Consistent YAML frontmatter properties (type, status, area, cycle) are the structural requirement that makes AI-built dashboards possible — unstructured notes can't be queried reliably.
- Building a working custom Obsidian plugin with Claude Code took about ten to fifteen minutes once the requirements were spoken through out loud.
- Screenshotting dashboard designs from Pinterest or Google Images and handing them to Claude Code as a style reference produces a consistent visual language across multiple plugins.
- Newly built or updated Obsidian plugins require toggling the plugin off and back on to register changes — a full app restart isn't needed after the first install.
- Speaking requirements out loud via a dictation tool rather than typing them let the builder describe a new dashboard in one natural conversational pass.
- The Metadata Menu community plugin turns frontmatter fields into dropdowns and linked-note pickers, adding light schema enforcement on top of plain markdown.
- Six separate purpose-built dashboards beat one giant dashboard because each area of a business needs a different visual shape to be useful.
Give notes structure, then let Claude build the view
WHAT TO LEARN
A markdown vault only becomes genuinely useful once every note carries the same frontmatter properties, because that structure is what lets an AI coding tool build a real dashboard on top of it.
- Plain folders and files are good for storing notes and letting AI read them, but bad for seeing the state of your work at a glance, you have to remember where everything is.
- Give every note in a system consistent frontmatter properties, a type, a status, an area, a cycle, before trying to build any dashboard on top of it; unstructured notes can't be queried reliably.
- Screenshot dashboard designs you actually like from Pinterest or Google Images and hand them to your AI coding tool as a style reference, so every custom view you build afterward shares one visual language.
- Build one small, purpose-specific dashboard per area of work rather than a single giant dashboard, a daily agenda, a content pipeline, and a project board each need a different visual shape.
- You can describe a new custom tool out loud in plain conversational language and have a working version in ten to fifteen minutes, without writing code or opening a terminal.
- Iterate in small conversational asks, can we do this, can we change that, rather than trying to specify the whole tool up front; each answer sharpens what you actually want.
Terms worth knowing.
- Obsidian Bases
- A built-in Obsidian feature that turns a folder of markdown notes into a filterable, groupable table view — useful but limited to that one table layout.
- Frontmatter / Properties
- A YAML metadata block at the top of a markdown file (fields like type, status, area, cycle) that gives an otherwise plain note structured data a dashboard can query.
- Hyo Agent plugin
- A free community Obsidian plugin, built by the video's creator, that lets you chat with Claude Code directly inside Obsidian instead of switching to a terminal or code editor.
- Metadata Menu
- An Obsidian community plugin that turns frontmatter properties into dropdown selectors and linked-note pickers, making structured fields easier to fill in consistently.
- Cycle
- The creator's term for her recurring quarterly planning period, tracked as a frontmatter property so dashboards can filter and switch between cycles.
Things they pointed at.
10:15toolVS Code (with Claude Code extension)
17:44toolMetadata Menu plugin
16:26toolPinterest / Google Images (for dashboard style references)
Lines you could clip.
00:09
“It turns out files and folders are great for storing things, not so great for finding them again.”
09:21
“Every time Claude just said, yes, we could do it.”
20:16
“So you don't have to put up with boring database views or hunting through folders trying to find things.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogy
00:00I run my whole business with a folder full of files in Obsidian. Every project, client note, idea, task, all of it lives in plain markdown files. And at first, that sounds simple enough, but it had one major problem.
00:11When I needed to find something, say, the client x project file, I was digging through folders to find it. And it turns out files and folders are great for storing things, not so great for finding them again. So I tried bases, the database view that's built into Asidian that you turn your markdown files into these database views.
00:27And don't get me wrong. Bases are better than trying to find things in folders, but they're still just a table view of notes limited to filters and groupings. Not to mention that they're kind of ugly.
00:37Sorry if you love bases. So I did what I always do, and I asked Claude Code if we could do something better. And now I have a bunch of custom plugins that allow me to view all of my notes in different ways so I can work from my notes and not just store them.
00:51So in this video, I'm gonna show you exactly how you can do the same. First, I'll show you the exact way that you should structure your notes so you can turn them into these customized visual dashboards. Second, how to use Clog code to make the dashboards, and you don't need to know anything in that code or touch the terminal.
01:07And number three, some things I learned along the way so you don't make the same mistakes that I did. And by the end of this video, you're gonna have a bunch of plug ins that let you view your notes in exactly the way that works for you. But before we jump in, what I'm showing you today is just one piece of something bigger that I teach in my membership community called the college of Knowledge.
01:26It is the place for solar operators who wanna build a personal agentic operating system, not just use AI tools, but build the actual system that makes AI genuinely able to operate beside you in your daily work. As part of the membership, you get access to all of our monthly workshops and build sprints where you actually build out the components of the system.
01:45You get access to our full toolkit library where every toolkit adds more capabilities to your agents, weekly office hours where our community is sharing wild things they are doing with their agents and the full resource vault with all my courses, templates, products, everything that I've ever created. So if you wanna stop playing around with all the scattered tools and build a real system that's gonna upgrade how you work, then check it out at the link description below.
02:09Alright. So like I said, Obsidian is actually a great tool for markdown files. And I do keep all of the parts of my business, all the knowledge for my business here in markdown files.
02:22It literally is a folder on my computer. I open it up here in Obsidian. So you can see here I've got horizons, which is where, like, I plan my year, my quarter, my weeks, my days, that kind of thing.
02:32I've got all the operations of my business. So all the areas of my business are in here, documents, improvements, insights, and issues related to everything in the business, meetings and people, projects, tasks, all of it.
02:44Right? All lives in these markdown files here. Right?
02:47And I have other domains, like, all of my knowledge lives in here, ideas that I'm creating, all of my content, all of my kind of operations. Right?
02:55But the limitation that I started to feel was that, let's say, want to look at my content. I come in here to the content that I'm creating, and there's no real way to see, like, where is this up to unless I, like, go into an individual note. So it's good for storage, and it's good for kind of, like, getting notes in, but finding notes again is hard.
03:14So that's where Obsidian bases come in, and I started to create a bunch of them. And I'll show you. This is like, let's say, this one is all my quarter two projects.
03:24Right? So, essentially, it's a table. It's sorted and grouped by a status.
03:29Right? So canceled, completed, running, snoozed, work in progress, which should probably be the other way that I just got clawed to create quickly.
03:36Right? But I'm the kind of person that looks at this, and I'm like, this is not very pretty, and I don't like looking at it. So instead, this is where I start to think, well, could I create custom plugins that show me kind of the same information but better?
03:48So I created, for instance, my projects plug in that looks like this.
03:55Right? So I now see the exact same info. Right?
03:58So you're seeing here, you know, pretty much the same kind of thing. But this one, the plug in that I built is actually dialed in and visual for me to be able to see.
04:08So things specifically that I built into this is I wanted to see, like, the cycles so I can switch between different cycles, you know, when a new cycle, you know, starts. I can see how many projects in total I have, how many are in motion, which means, like, they're either work in progress or running, how many are up next, how many are completed.
04:26I can see, like, the progress of how I'm getting through the quarter. And then in each of these, I can actually see the progress of the tasks that are completed compared to the tasks that are not. I see what areas they're in, and it's a completely different view.
04:41And if you're a visual person, I just think that something like this works way better than something more like this. And maybe you can turn bases and make bases prettier and that kind of thing.
04:52But it was just as easy for me to build this custom plugin as it was to try and figure out how to make bases better. Right? And the other thing that I like is I can actually drag things in between.
05:03So if it's finished, I can do that. I can also right click and change the status. And all of that, I just build by asking Claude code.
05:09Right? And then I can click into any one of these and actually get to the note itself. Right?
05:14And I have a bunch of other plugins that I built exactly the same way. So I have a plugin for my knowledge. So this is where everything that I'm saving, like articles, videos, that kind of thing, they come in.
05:25I save them in here. I get called every night to read or watch, like, get the transcript of the video and give me a bit of a summary, right, of it. I can then choose to ingest it into my knowledge, and then I see all the process things here.
05:39And because a lot of my notes aren't just kind of, like, dump this note in here, they actually require a process. Right? A project requires a process.
05:47You know, I even have a plug in that's sitting here at the moment, which is for all of my content. So it pulls from the notes that are in my content folder.
05:56Right? Atomic content, newsletters, YouTube videos, that kind of thing. And it pulls it into all of these different views.
06:03This is probably the one that is built out the most, but essentially have anything that is in the ID Bank. So if I click on one of these, it's sitting here in a content status of incoming. But then I also can see ones that are up next.
06:17I can look at them in horizon. So what content is going out this week compared to next week compared to the future. I have a pipeline so I can see everything that's kind of in status, calendar, like, different ways.
06:28So there's so many different ways to view all of the notes that I have and is visual. It's also like, I can filter so I can see everything. I can see just YouTube.
06:39I can see like, I can turn these on and off. And it just makes it so much more of a joy to work with my notes. And, essentially, it's turned Obsidian into a place where I can actually do work and not just store things.
06:52So that's kinda my projects, my content. I have another one over here.
06:56If we close this up, that is my I call it my daily OS. Right? And at the top, it's got a calendar.
07:03So I can see kind of, like, you know, days and things like that, and I can go back through it. I see where we are at in the quarterly cycles. At the moment, I'm in a cycle break, and the next cycle starts in seventeen days.
07:14And that is being pulled in because in my horizons folder, I have my quarters in here.
07:20So it kind of reads when the quarters are, works out the dates, that kind of thing. And that's something that, you know, a plain markdown file or a base cannot do. Right?
07:28So there's actual kind of, like, not intelligence, but formulas kind of built in so that we can see these views. It also then comes up with my agenda for the day. Right?
07:38And so all these, I can move these around if I wanna show this. And so I can see at a glance quickly everything that I have to do for today. I keep all of my tasks in here.
07:46I also have a button here that I can create a new task really quickly. And then down here is all the notes that I've created in that day. So I don't use a day page in Obsidian.
07:56I just found that, again, I was trying to make something happen in a markdown file that just was kind of annoying trying to pull all my tasks in for the day. You know, any notes that I created, I was like, it just wasn't working for me. So I decided, well, why don't I just create a plugin for this that gives me everything that I will see?
08:13So I can then also come here and create any kind of new note, like the main notes that I create every day, documents, projects, quick notes, sources, spark notes, atomic ideas, you know, that kind of thing. And so I can go back through all of my days. I can see what I had on that day, what I did, what I had to move forward, and then all the notes that I created.
08:33And so this really just becomes kind of like a day page in that I can just go back through and kinda see what I was doing on those days and that kind of thing. And this is probably my favorite one.
08:42And, literally, all I did was just keep saying to Claude, okay. Could we do this? And could we add a filter button so I can filter by just, you know, atomic ideas or just this other thing?
08:53And every time Claude just said, yes. We could do it. And so I'm finding these plugins absolutely invaluable as I use , and it's made it way, way more usable.
09:08Alright. So the thing that makes this possible to build these custom plugins is actually using Claude code with Obsidian. Okay?
09:15Now please don't get freaked out by Claude code. Right? Essentially, it's just like using Claude, but it has kind of superpowers where it can actually do coding.
09:25And that is important, one, when we're building these plugins. But, also, I've just found it useful just in general building out my Obsidian workspace. So I've tried to use Obsidian heaps of times in the past and just felt like a lot of the things I wanted to do felt a little bit too complex.
09:42And not even complex, but kind of fiddly. So, like, even things like this, like, in each of my areas, have down here, like, bases that are actually embedded into the area.
09:52So I can see, like, what are the threads for this area? What are the issues, the improvements, that kind of thing? And instead of actually trying to build those myself, all I do is say Claude code, hey.
10:01Can you insert a base into that document that shows me this, this, and this? And so even just things like that, it just becomes easier when you use Claude code with Obsidian. Now so there's a few different ways to do that.
10:13A really popular way if you don't wanna use the terminal. Like, I'm not a terminal person. Don't wanna use the terminal.
10:18I would suggest either getting something like Versus Code. So this is what Versus Code looks like. And what you can do with Versus Code is actually install the Claude code plugin.
10:28So when you go here and you chatting with Claude, it is just like chatting, you know, within a normal conversation. It doesn't look like terminal at all. The other way that you can do it is you can come to your Claude app and you just come over here to code.
10:42And then all you have to do is open up so see how this says, Chad? You wanna open the folder, the same folder that you're opening in Obsidian. Okay.
10:50So I would come here. Mine is called FHQ. I'll just open that up, and then I can go trust, and I can just do anything I want and talk to it about anything that I wanna do.
11:01So that's probably the easiest one if you already have Claude code. Now if you're already using Obsidian, if you watched my video last week, you would have seen me talk about this.
11:08But I created a plugin. It's called the HyoAgent plugin, and, essentially, it lets you talk to Claude code from within Obsidian.
11:16So if you wanna grab that, I'll leave a link for it in the description below, and I'm gonna use that to build out this next plugin that I'm gonna build. Okay? So this next one and I wanted to show you how easy this is just to do in conversation and to be able to add new features, change things, you know, that kind of thing.
11:33So this new one I want is basically an areas view. So I wanna be able to view all of the areas in my business. So the same ones that you're seeing here.
11:41Right? And within each of these areas I showed you that I have notes connected to them. I basically just put quick notes into my system, and AI organizes them into things like initiatives, which are projects that we're working on, threads, which are kind of like more thinking and ideas that we're building, issues, improvements, and insights.
12:00Right? And so what I want I don't mind this, but, again, I want something that is a little bit more visual. So I wanna take each of these and turn it into a plug in where I can basically see all of the areas of my business and then each of these things kind of broken down.
12:14Right? So all I'm gonna do is I'm gonna use this whisper flow to tell Claude exactly what I want. So I'm gonna do that now, and I'll speed it up so that you don't have to listen to me kind of waffle on for the next few minutes.
12:27And then you'll see kind of how easy it is to build this out.
12:34Alright. So I've just, you know, talked that through with Chad, and I'm gonna put that over to him to see what he comes up with. Okay.
12:41So he is getting to work. So he's basically reading kinda like the area template. He's reading kind of some of the other plug in code.
12:49That's what kind of all these JSONs are, and he's just getting to work. Alright. So Claude has built everything now.
12:56So full disclosure, probably took about ten minutes, and there's just a bunch of stuff that he has just kind of laid out about, you know, what it includes, that kind of thing. Now when you build a plug in like this, if you're inside Obsidian, like, building it in here, you have to actually quit and open it again because that then just registers the plug in.
13:14So once we're back open, we should be able to come here and see what we have. So now we have Areas OS. Okay.
13:20So it's already turned on. And then if we come down here so you can see that I've got all the areas across the top, which is why I asked. There's a description which actually comes from the file itself.
13:31And then within here, we have all of the different sections that I wanted to see. Okay?
13:38So quick notes I've taken about business ops, insights, improvements, issues, threads, initiatives. If we come here, we can see kind of all of that. And the reason that I wanted to build this, and this is, like, one of my, you know, college knowledge membership, which is, like, one of the bigger things in my business, is that I essentially every week, every month, every quarter, I go through each of these different areas, and I look at what are the initiatives, which are essentially the projects that I'm running.
14:04What are the threads? Like, threads are kind of, like, ongoing conversations that I'm having with AI about things. And then I also look at these down here, which is issues, improvements, and insights to, and they really guide me in terms of what should I be working on next.
14:18I wanna try and solve issues really fast. I want to build improvements in. I wanna kinda do insights.
14:23And so now I've got, like, a really much nicer way to kind of view this without going into that messy markdown file. Okay? Now one of the things that I'm looking at and I'm saying, you know what?
14:36I don't really love this. And this is where you can start to kind of really dial things into the way that you want. So let's say this is marketing and funnels.
14:44I'm seeing a bunch of, like, completed stuff here within initiatives. So I'm thinking, you know what? Once I start to get a lot of different projects in here, I don't wanna see all the completed ones, really.
14:53So I might want to ask Claude to hide those and the same for kind of, like, threads and things like that. So I actually think that instead of kind of having these as kind of sections that open up, that I might want them as kind of, like, tabs, like, within here that I can open up and, like, essentially have them grouped in different ways within there.
15:13So I'm gonna ask Chad to do that now. So I'm gonna come back to the same conversation. I'm gonna say, okay, Chad.
15:19Yeah. I really like kind of where we're going with this. I think that what I wanna do is not have each of the sections within the business areas as accordions.
15:29I would rather have them as tabs so that let's say I can open up initiatives. And within initiatives, I can see the breakdown and the grouping of work in progress, snoozed, completed, that kind of thing.
15:41And same for all the rest. So if there's a way to break them down by status, we should do that. Otherwise, I'm gonna see a lot of, like, for instance, completed projects that I don't really need to see.
15:50So I think that I'd like to make that change. Alright. So and what I want you to kind of, like, get here is that whatever you want, you just keep kind of, like, saying to Claude code, can we do this?
16:02Can we do that? Can you change it this way? That kind of thing.
16:05And the more that you kind of build out dashboards like this, the more you'll kind of, like, know how you want things to actually look. Okay? So a lot hard work on that.
16:15I wanna talk you through a couple of different things I learned along the way. So I think that it's really important to think about how you actually want these dashboards to look. So I went on to Google images.
16:26I went to Pinterest, and I just kinda, like, typed in dashboard lab visuals or dashboard UI. And I screenshot a few different, like, things that I like.
16:36And I gave that to Chad, who is my chief of staff, who does all this stuff for me. And I said, like, let's create an actual kind of, like, style guide for these dashboards. So every single dashboard kind of ends up having the same style, which is good when you kind of have a few of them because you don't have to keep explaining like, oh, I don't really like how you did that.
16:55I don't really like how you did that. The other really important thing that you want to make sure you get right is actually making sure that your markdown files are structured in a way that makes building these plugins easy. So if we have a look at, let's say, one of my area files is that I have properties set up in each of these.
17:16And so this one is the type of an area. There's a description. But if you come down here and we have a look at, let's say, the initiatives that are running, right, in my project files, we have properties like the type is project.
17:29We have a status, right, where I can change the status. We have the area that it's connected to. Okay?
17:34So that's one of the kind of eight areas of my business. We have the cycle that it's running in. And so having these properties means that when we go to create dashboards, there's structure that it can pull things in.
17:47So it can pull in all of the cycle two projects because we have a property for that. It can pull in all the projects in an area because that's linked in the properties. So I use a plugin called the metadata menu plugin that created all of these kind of drop downs, links, that kind of thing.
18:04But you can just create properties yourself and type things in, but I just use Claude code to create all of that. And so each of my note types has these properties that, like, brings structure to kind of a plain markdown file.
18:19So that's another really important thing that if you wanna build these dashboards that you need to get right. Okay. So Chad's finished that.
18:27Now when you're updating these, you don't have to restart Obsidian every time. You just come in here and you turn it off and on, and then you'll see it come up again. So now we have kind of along the top here, and then we've got tabs within each of those business areas.
18:40So we've got threads. We've got issues, improvements, insights, quick notes. And then if we come here to one let's go here.
18:48Within here, now we have groupings. So I can actually see what's work in progress, what's running, and then completed is actually closed. So it's much easier.
18:57And so you can see that all you have to think about is, like, how would it be, like, better to view this, essentially? So now I have an area OS plugin. It took us, like, ten minutes, pretty much, ten, fifteen minutes to figure out what we wanted, get ClaudeCode to build it, and now I can come in here every week and actually visualize all the parts of my business, what's running, what improvements I need to make, what issues we have coming up.
19:22And it really is quite wild that all of this is just pulled from markdown files. So if you are the kind of person who needs to visualize the stuff that's going on in your business, visualize your notes, I would absolutely suggest getting in and creating something. Start with something simple like, you know, I've got my project board here, and then build up to maybe something that manages your day and whatever other way that you can imagine to visualize your notes.
19:51So you don't have to put up with or hunting through folders trying to find things. A quick conversation with Claude Code, and you could be building out these amazing dashboards for your notes. But views are just one part of how I turned Obsidian into my ultimate agent operating system where I run my whole business.
20:07So if you wanna see the full setup, I went through everything in this next video that you should definitely watch. And like I said, if you wanna start building out your own agent operating system, then check out the College Knowledge membership in the description. And, of course, if you liked this video, make sure to give it a like and subscribe so you see more of content like this in your feed.
The Hook
The bait, then the rug-pull.
She runs her entire business out of a folder of Obsidian markdown notes, great for storage, useless for actually seeing what's going on, so instead of settling for Obsidian's built-in table view, she asked Claude Code to build six custom visual dashboards instead.
Named ideas worth stealing.
00:42list
Six purpose-built dashboard plugins
- Daily OS
- Content OS
- Knowledge OS
- Project OS
- Areas OS
- Threads OS
One dedicated plugin per major area of the business, each reading the same markdown vault but rendering a different visual view (progress bars, metric cards, grouped or tabbed sections) instead of one generic table.
Steal forany Claude-Code-built internal tool that needs multiple purpose-specific views over one underlying data source
17:26concept
Property-driven note structure
- type
- status
- area
- cycle
Every note carries consistent YAML frontmatter properties so Claude-Code-built plugins can query, group, and filter reliably — plain unstructured markdown can't support real dashboard views.
Steal forany notes vault, CMS, or flat-file system you want an AI-built dashboard layer on top of
How they asked for the click.
VERBAL ASK
01:30product
“check it out at the link description below”
soft mid-intro pitch for her own paid College of Knowledge community, framed as 'what I'm showing today is one piece of something bigger,' repeated as a closing link-in-description CTA at the end
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
