How To Easily Organize Projects & Tasks With Obsidian Bases 🚀 📝
By Wanderloots
Summary
## Key takeaways - **New Bases Update Enables Direct Note Creation**: The new Obsidian Bases core plug-in got some major updates this past week that make it more powerful than ever. You can now add new notes directly to bases, gaining all of the properties that were in that table view. [00:00], [00:06] - **Use 'Kind' Property for Clean Filtering**: Rather than using tags, create a new 'kind' property like project, epic, story, task to filter files into the project management base where kind is not empty. This cleanly separates project files from the rest of the vault. [08:38], [09:04] - **Hierarchy: Projects → Epics → Stories → Tasks**: The idea here is that we have the overarching project within projects you have epics within epics you have stories within stories you have tasks. For example, blog project has 100 days writing epic, each article is a story, with tasks like ideating, outlining, writing. [06:45], [07:06] - **Predefine Properties in Templates for Bases**: Create a project template with all desired properties like status, priority, due date first, so they appear selectable in the base table instead of only as formulas. This allows proper types like list for kind and status. [09:24], [10:13] - **Dynamic 'Days Until Due' Formula Property**: Take the due date property labeled 'due' and use 'do relative' to create days until due formula that automatically calculates like 'due in 4 days' based on current time. [23:00], [23:14] - **Promote Ideas Through Hierarchy via Kind Changes**: Add a new idea with kind=idea to the inbox view, then upgrade it by changing kind to project, epic, story, or task; it automatically moves to the corresponding filtered view in the base. [21:28], [22:03]
Topics Covered
- Bases Close Notion Gap
- Project-Epic-Story-Task Hierarchy
- Kind Property Trumps Tags
- Dynamic Embedded Dashboards
- Idea Inbox Promotion Flow
Full Transcript
The new Obsidian Bases core plug-in got some major updates this past week that make it more powerful than ever. You can
now add new notes directly to bases, gaining all of the properties that were in that table view. This effectively
turns bases into a template generator.
You can also introduce dynamic functions based on a very easy to understand time syntax. So, you can add dynamic
syntax. So, you can add dynamic properties to your tables. These
features make using Obsidian as a project management system much more feasible than ever before. It's really
closing the gap between Obsidian and Notion now that you have the ability to manage projects inside of Obsidian. In
today's video, I'm going to walk through how to set up a full project management system for both projects and tasks within Obsidian using the bases core plug-in. I'll also walk through some of
plug-in. I'll also walk through some of the latest updates on how you can make your tables your bases more powerful.
Hi, my name is Callum, also known as Wandloots, and welcome to today's video on how to build a project management system inside of Obsidian using the Bases core plugin. When I switched from Notion to Obsidian, the biggest feature
that I was missing was the ability to use a table and instantly add a new note to that table that gained all of the properties of that table. So, you knew that that new note would always be filtered properly in that table, helping
you keep track of a lot of different types of project architecture. Now that
Obsidian has this feature with the basis plugin, I'm excited to build out my project management system inside of Obsidian with all of the power of Notion, but with the added benefit of doing it in Obsidian with Markdown and
being able to connect to all the other plugins. When I heard about this new
plugins. When I heard about this new update, the first thing I thought about doing was building a project management system. So, I'm excited to walk through
system. So, I'm excited to walk through how I set this up for myself and how you can do the same. I've actually been using Obsidian to organize my projects a lot over the last couple of months. So,
this timing has been perfect for me to be able to properly build bases in with project management functionality to the projects that I've already been working on in Obsidian. In particular, I'm going to start a project where I write 100
articles maybe in 100 days. That's kind
of my goal. And I'm also working on building an app and an Obsidian plugin that will hopefully help you a lot because it's already been helping me a ton. So, I'm excited to announce that
ton. So, I'm excited to announce that more in a couple weeks. For now, I'm excited to be able to use bases with all of this new functionality and show you how you can do the same. If you find this video helpful, I would love if you would please consider liking and
subscribing as your support really means a lot to me and you do continue enabling me to make these videos. So, thank you very much. Also, I want to note that I
very much. Also, I want to note that I will be making all of the bases that I talk about and build in this video available for my paying YouTube members.
So, if you want to get an actual copy of this template, so you don't have to start from scratch, please consider joining my membership and I will be happy to give you that template. Now,
let's dive into project management using Obsidian bases.
So, today's video is going to focus more on the actual practical building of project and task management bases, but I've made a couple other videos on bases. In video one, I did an intro to
bases. In video one, I did an intro to bases where I talked a lot more about what they are, how to get them set up, the key features, practical examples, and then a comparison of bases to data
view and notion. And then I talked about a coming soon section that actually came true. So, in video two, I walked through
true. So, in video two, I walked through the new features, which there's quite a few updates here that if you're interested in learning more about the philosophy of what's happening with bases and where it's going and why I think it's now actually getting to the
point where you can replace notion with it, then I recommend checking out video two because I walk through a little bit more in depth on how all of the different features come together. And
today, I want to focus on specifically building a project and task management base. So, this is something that I've
base. So, this is something that I've been trying to figure out how to use Obsidian for for a while. I previously
used notion for building out some project and task management, but I haven't used notion in a while. So, my
Obsidian project management has been a little bit lacking. And today, I'm going to fix that. I'm going to do a full walkthrough example of the new features of how the different updates to bases allow me to finally build out my project
management system that I've been hoping for in Obsidian. So today's video, we're going to walk through how to enable bases, how to turn on the plug-in if you haven't already. We're going to create
haven't already. We're going to create an overarching project base. We're going
to create a task base, and then I'm going to show you how you can set up views and filters so that you're able to aggregate all of your project management in one place. We can consider all of that phase one, which is the setup of
the bases and the ability to use the new features. Then I'm going to get into
features. Then I'm going to get into phase two, where I talk a little bit more about how you can add complex dynamic properties that automatically update based on things like time. And
then finally, we'll get into phase three where I'm actually going to show you how I use AI to assist both with building bases and planning out my projects. This
has been one of the most powerful ways that I found to boost my ability to keep up with my projects and actually get my tasks done. So, I'm excited to show you
tasks done. So, I'm excited to show you how this all fits together.
Okay, so the first thing that we need to do is we need to enable bases. So, I
walked through this a lot more in video one, how you can get access if you are not on the early access because this is available only for Catalyst members at the moment. So you can see that this is
the moment. So you can see that this is under Catalyst license. So you can only get access to this if you are a Catalyst member. They're doing a lot of trial and
member. They're doing a lot of trial and error and iteration of this basis functionality before getting into the full release to everyone. But that
doesn't mean you can't start building.
You can get the Catalyst license if you want to or you can start thinking about how you're going to organize your system to tap into this functionality. So I'm
going to quickly update the app. You can
see that the smart connections is running on the side here which is a way for me to create a vector database of my entire vault. So I can use local AI to
entire vault. So I can use local AI to search. So I have another video that
search. So I have another video that walks through smart connections if you're interested in seeing how that works. You can also add images directly
works. You can also add images directly as an inline component. So that's an interesting feature and I talk about this more in video 2 where I've updated
it to reflect the latest 1.9.4 updates.
So I recommend checking out that video if you want to learn more about how all of these features work. But now that I have updated it, if we go to the side here, there's a core plugins and we have to have bases turned on. So that
completes step one and now I want to create the meta project base.
Okay, so I actually just went through this whole tutorial and when I went to go add properties to the table, I realized that when I went to go just click add property here, the only way that it would add a property from the
base itself was as a formula. You see
there's this formula field here. So now
we have this new property and it's a formula, but it doesn't have the ability to have the property type like text number, list, date and time, date, and checkbox. So that makes it really
checkbox. So that makes it really annoying. Then when you go into a
annoying. Then when you go into a project like this example one that I created here that I'm going to get more into in a moment, you want to have a list type for tags. And same thing with status, you potentially want a list
type. And for due date, you want it to
type. And for due date, you want it to be date and time. So there's all of these limitations it seems at the moment where the default property creation within the table itself is only as a
function. So I took a step back and I
function. So I took a step back and I created this new diagram here that I took some time to reflect on and create so that it could be a little bit more streamlined for you here.
The idea here is that we have the overarching project within projects you have epics within epics you have stories within stories you have tasks. So, I'll
walk through this more in a moment. I
just wanted to give you a quick overview on what it is we're actually going to be building here. And the goal here, the
building here. And the goal here, the idea is that for each project, for example, my blog, that could be a project. Within that blog, I have an
project. Within that blog, I have an epic, which could be my 100 days of writing experiment. Within that 100 days
writing experiment. Within that 100 days of writing experiment, that epic, each article I write is going to be a story.
So then within each article there could be the task of ideulating of outlining, writing, editing, publishing. So those
would all be tasks that fit within the single episode or article that fit within that overarching epic of the 100 days of writing as part of my wanderloots.com website building
project. So rather than just showing you
project. So rather than just showing you how to build out the base, the project management base itself, I actually realized that it's going to be more effective for me to show you how each of these individual pieces fit together
into the overarching project management system that we're building here. And
then I will integrate how we can use that to optimize our template creation, for example. So let's get going.
for example. So let's get going.
So, we were just about to add properties here into the existing project space, but I'm actually going to just quickly create a new project management base, and this will make more sense in a moment. So, here we go. We're back to
moment. So, here we go. We're back to all of the files in the vault here. I'm
going to quickly call this one project management. And now, rather than just
management. And now, rather than just jumping into organizing the base itself, I want to create the core file type or kind of file that I want to be filtered into this project. So, let's do that on
the side here. So, we're going to call this project template. We're going to move this into the templates folder. And
then I'm going to add a new property.
So, we're going to call this kind. Now,
this could be type, this could be style.
The word here doesn't matter. What
matters is that actually rather than just trying to use something that fits into my existing system, I'm creating a new property type that has nothing in it that no nodes are connected to. And I'll
explain why in a moment. The general
idea of this is that I'll be able to go into my project management base and the filter rather than saying oh where tags contains project or tags contains tasks
I can instead just say where kind exists. So we're going to give this the
exists. So we're going to give this the kind type of project. And now if I go back to my table my base on the side here I can go filter and I can just say
where kind is not empty. And right away it just filtered my entire vault to only have this new project template. So if
you remember, I have this list of properties that I want to add here. So
the goal here is to create this project template in a way that would it will allow me to add all the properties very easily to my base because like I mentioned earlier, if I don't do that, I
will only be able to introduce functions from the table. So we need to make sure that the properties that we want included inside of our base exist in the file already, which is why I'm going to create this initial project template. So
here we have the kind, which is like the type of file. So this would be either project, epic, story, task. I'll I'll
get into this more in a second, but each of these is a kind or a type of file.
Then we want to add status, priority, due date, tags, cover image, description, topics. So I just quickly
description, topics. So I just quickly went through and added all of the different properties that I think would be useful for organizing a project file.
So this has now become my project template. But what's cool is by adding
template. But what's cool is by adding all of this in here, if I go over to properties on the side, because this project file, this template exists inside of this table, all of those properties just appeared in the list of
selectable properties to add to the base itself. So rather than going into filter
itself. So rather than going into filter and like I mentioned having it be some complicated tag filter, which I found actually I was running into a lot of problems with, I can instead just say
where kind is not empty. So for me now, kind or type or whatever property you want to use for your project management system. I'm only going to include this
system. I'm only going to include this property in files that I want to be organized inside of projects. For
example, a daily note might not be something that I want to include inside of a project. So I just won't give it the kind property, which means it won't appear inside of my project management system. So by doing this, I'm able to
system. So by doing this, I'm able to actually very cleanly separate my new project management system from the rest of my vault while maintaining everything in one vault. So now what's interesting
is if I go over to the table here, the project table, I can start to add in all of those properties I just added. And by
toggling those all on, they now all appear in the order I clicked them on in here, which is the order that matches this project template.
So what's cool is rather than using this project template to create a new note, for example, command N, new note, and then command P, insert template, and then project template, which now then
produces it inside of this project management system, the project example.
I could instead just click new and it already has everything in here that I'm looking for. So I could just say project
looking for. So I could just say project example 2 and just put kind project. And
now it would fit perfectly inside of this system. So, it just saves you a
this system. So, it just saves you a couple steps to be able to click the new button to quickly add a note into your existing table with all of these properties that are in there. And if I make any changes to these properties,
for example, maybe project example one is highest priority. I can toggle that as high. And for project example two, I
as high. And for project example two, I can give it as medium. And if I go click into the note, I've now modified that file property. So you can use this base
file property. So you can use this base as this literal home base or database for you to go through and quickly fill in all of the relevant information all in one spot. So now let's go into the
next stage here. And I'm just going to quickly fill out all of these different templates and then I will show you how I integrate that into my overarching table here.
And if we just take a quick look back at the core hierarchy here. So we have our overarching high-level project which is broken up into epics which you can kind of think of as major phases of the
project and then within each epic you have the story which is then broken up into tasks. So this just provides this
into tasks. So this just provides this really nice flow where you have your overarching system you have your major phases you have your individual major tasks and then you have your subtasks within that major task. And I'll get
into this more in a moment, but the idea is that we'll also introduce an idea kind here where the idea can be linked to a project. It can be turned into a story. It can be turned into a task or
story. It can be turned into a task or an epic. So you'll have this singular
an epic. So you'll have this singular idea inbox that can be implemented anywhere in your project hierarchy and it can be promoted to any particular type. So this will also turn our entire
type. So this will also turn our entire project management base into an idea inbox. Okay. So now let's create the
inbox. Okay. So now let's create the epic which is the next layer. So this is easy. I'm just going to press command P,
easy. I'm just going to press command P, duplicate current file, and we're going to call this epic template. And what's
nice is by duplicating that after I've already moved it into the proper templates folder, the Epic template is already in the template folder itself.
And here, we just need to switch this to kind epic. And I'm going to add one more
kind epic. And I'm going to add one more property here, which is parent. And
we're just going to use this to link to a project. So the parent of this epic is
a project. So the parent of this epic is the project. And a parent of a story is
the project. And a parent of a story is going to be an epic. A parent of a task is going to be a story. But, and this is one thing that I realized would be very helpful. It's also valuable to create a
helpful. It's also valuable to create a project link directly within these categories here because then that will enable us to sort by project or by parent depending on what level you want
to look at in your hierarchy of your project management system. So now I'm just going to duplicate this again.
We're going to call this story template kind story. And that's it. Duplicate
kind story. And that's it. Duplicate
again. We'll call this task template.
task idea template kind is idea and then if you're ever getting into coding or developing or building you probably are going to have bugs. So we can create one
more template called bug template. So
now if we look at the side here in our base we can see that we have the different kinds of files that fit into our overarching project management.
So this is starting to get a little bit messy which is where we can introduce a new view on the side here. So by
clicking on this little grid in the top left here, this is the view display where I'm able to go in here, click table, and I can change this to configure view. And we'll call this all
configure view. And we'll call this all project management files. So this filter here that we've applied to all views is just where the kind type the the kind
property is not empty. But let's say we want to take a quick look at only our project files. And just before I do
project files. And just before I do that, just before I click duplicate, we I forgot that we have a new property here. So we can add parent and project
here. So we can add parent and project here. So these are two more properties
here. So these are two more properties that we can drag over just for organization purposes. And actually just
organization purposes. And actually just before I get into showing you how to duplicate the view, I want to show you that for example, if I click into one of these properties here, like the parent property, it doesn't give me any
prefilled wording to put in here. But in
priority, it does. It gives me high and medium. And that's because I have
medium. And that's because I have projects, I have files that have already used this particular property. So if we want to be able to automatically fill in, for example, kind, what we need to
do is we need to turn this kind property into a list so that I can create one example node that has all of the properties within it. So we can actually do that from here. Now I can right click on this and I can change the property
type to list. And you can see over here it changed and here it changed. Now if I click into one of these spots, it pulls up all of the possible kinds that I have already included here. So it's better to
use a list type property for this type of system because it makes it very easy for you to now just click new test note and I can give it a type of project and right away the test note gets added
here. If I remove that project type kind
here. If I remove that project type kind here it will be removed from this table because the filter here is that kind is not empty. So we can do that for all of
not empty. So we can do that for all of these different fields here. The ones
where for example priority we probably want to keep it at high, medium, low but there is no low option here. So I can either add that to one of these existing nodes or I can create a new node here.
We'll call it test properties. And I can go through and I can introduce all of the statuses and all of the priorities that I want any of the consistent properties that I want to be automatically filled here. So we can
give this one for example high, medium, and low. And now if we go back to the
and low. And now if we go back to the project management, if we click on this section here, you can see it's now giving me the option between high, medium, and low. So we can do this for all of the fields that are relevant.
Maybe for status we want to have backlog unstarted, in progress, completed. And
because I know I'm going to be using this specifically for writing, I will also have researching, outlining, drafting, editing as additional statuses. And now if we go back to our
statuses. And now if we go back to our project management, if I click on status, I have this full list that I can just quickly click on. And that makes it very easy for me to change the status of a particular note within the project
management ecosystem. But as you'll
management ecosystem. But as you'll start to realize here, it's getting a little bit hectic. So I'm going to go up to the top here to all views and I'm going to say add filter where kind is
not test. And that just removed my test
not test. And that just removed my test one from here. I'll do the same thing for template afterwards. But let's
create a few more notes and a few more views so you can start to see how this fits together a little bit better.
So if we go up to the top left here, we have only one view at the moment. This
single view has been filtered for all views here where kind is not empty and kind is not test. So what we can do is we can start getting into this view this portion right here where we can
implement view by view limitations view by view filters. So let's go here and I'm going to click duplicate on this little arrow here because by doing that all of these properties will get brought
in. So, if I didn't if I just clicked,
in. So, if I didn't if I just clicked, for example, add view, you can see that it starts off with nothing in it aside from these major filters that we have on all views up here. But that's kind of annoying because now you have to go
through and click all of the properties that you want. So, instead, I'm just going to delete this one. We can click on the side arrow here and click duplicate view. And we'll call this one
duplicate view. And we'll call this one all projects. And what that does is it
all projects. And what that does is it keeps all of the properties here and it lets us go in and now just add a single filter for this particular view where kind contains project. And now you can
see that it's pulled in all of the files that only have the project kind. And
what's nice here now that I've included this filter here where kind contains project, if I click the new button, it pulls in that kind already. So it will add a new note that exactly can be
filtered into this particular view. So
that makes it a really easy way for me to start using this new button to just instantly add a project or what will more likely happen instantly add a task.
And this is why I wanted to combine the projects and the tasks bases into one singular base because all we need to do is just change the filter type in order to have that base be built into our
project management system. Let's create
a view for each of the key components, all of the kinds or the types of the project management system.
So I'm going to go here. I'm going to duplicate this view again. We'll call
this all epics. And then I just need to go up here and change the filter to where kind contains epic. And that
filtered it right there. So it's very easy to begin once you have your base system set up, your core organization with all the properties that you want to have. Just go through and quickly
have. Just go through and quickly duplicate the views. All stories, filter for story, all tasks, filter for task.
And again, you can kind of see why using kind rather than tag is a little easier here because I might have hashtag task somewhere throughout my vault. And it
starts to get a little bit more complicated when what I really want is an inbox for my tasks that are part of my existing project management system.
And there we go. I've now gone through and added a view for all of those different components. So now if I want
different components. So now if I want to add a new epic, for example, I can just quickly click on all epics and then click a new plus button and a new epic will appear with the kind already pre-filled. So you can see now if I have
pre-filled. So you can see now if I have a new task, I could say, okay, I have this new task. I go down to my tasks view, click new. Boom, there's already a new task here and I could say whatever I want. I can link it to a particular
want. I can link it to a particular project here. I can link it to a
project here. I can link it to a particular epic if I wanted to or a particular story and it starts to automatically fill in all that information as I go here. So, I'll
explain the parents section in a moment, but the key thing here is that we really want to have the project built into all of this because in the future when you have a 100 tasks here or a thousand tasks, you want to be able to just click
this project button and it will group all of your tasks associated with a particular project. So effectively what
particular project. So effectively what we've just built here is the ability to introduce a project, an epic, a story, a task. And we can move all of this
task. And we can move all of this through an existing system of promotion where you could have a new idea that relates to a specific project that is a particular task that fits in with a
story or an epic.
And you could just take your idea that you have here. We could go to the idea section and say, "Oh, I have a new idea here." Okay, idea. Maybe my idea is
here." Okay, idea. Maybe my idea is create new Obsidian plugin because this is something that I'm working on right now. So, I can add this here. It gets
now. So, I can add this here. It gets
added to my ideas table. If I go back to all of my project management files, as I'm looking through this, I'm like, "Oh, you know what? This new Obsidian plugin is actually not just an idea. This is a full project in and of itself." So, this
is where my idea can be either linked to a project or converted into a project. I
can just take this create new Obsidian plugin and rather than have this be kind idea, I can change this to kind project.
And now this idea that I had was just upgraded to a project that now goes into my projects view. So it becomes very easy for you to change one type of file to another as you promote it throughout
your ecosystem. So now there's one more
your ecosystem. So now there's one more thing that I want to show you before I get into an actual example of walking through this idea flow or more of these concepts that I have on the side here as
graphics where you can link ideas to different projects. You can start to
different projects. You can start to identify tasks etc. And the main thing I want to add here is what's cool with the properties in the base. I know I mentioned at the beginning that when you add a new property, it automatically
turns into a formula, but because we're dealing with project management and we have things like due dates, for example, you can actually start to use these functions to introduce a dynamic element to your table.
Just a quick reminder to please like and subscribe as you watch this video if you find it helpful because that really does help me continue to make more of these videos in the future so I can hopefully
help you out more. Thank you.
So let's say we have days until due.
What we can do is we can just take our property of due date that is specifically labeled due as a single word because I can just go do relative and that will create this new property
here days until due so that if I go to create new obsidian plug-in project and I change the date to I don't next week automatically this property appears and it calculates this is due in 4 days. So,
this is a cool way that you can bring a dynamic element to your project management. And I don't want to get too
management. And I don't want to get too into that because there's a lot that you can do with it. And I'm going to talk more about how you can use AI to help you with this. But there's a whole list of syntax here specifically on basis
functions where you can use a lot of dynamic code to, for example, pull in all of the files that are listed as links inside of that note. So, it
becomes a very powerful way for you to effectively use code to add dynamic components to your table. And I talk about this a lot more in the second video in this series on the updates to the Obsidian Bases core plugin. So I
recommend checking out that video if you want to see more about how you can use functions. So now I want to quickly show
functions. So now I want to quickly show you how these different files can flow together a little bit better.
So let's just use the templates as an example where the project itself will be the template. So you can see that
the template. So you can see that project template this doesn't have a parent because the project is the highest level of the ecosystem here. So
we can leave this one blank for now. But
if we go to the epic template, we can say that the project is the project template. And in this case, it would
template. And in this case, it would actually be the same here for the parent. And the same with story, but for
parent. And the same with story, but for the story, the parent would be the epic template. For the task, the parent would
template. For the task, the parent would be the story template. So you can kind of start to see how these start to fit together with the hierarchy. I can see not only which project this task fits
within as the overarching system, but also the immediate story that it's related to. But as you may have noticed,
related to. But as you may have noticed, it starts to get a little bit hectic here, especially when we're looking in this all project management views. It
gets a little better when we get into tasks. But this still doesn't let us
tasks. But this still doesn't let us group by project.
So this is where what we could do is we could create a new view for each project we have. So that when you click on it,
we have. So that when you click on it, it automatically filters as another layer here for that particular view only for that project. so that we can get an at a glance view of all the tasks associated with a particular project,
all the stories, all the epics, etc. But rather than do that, what we can do instead is we can create a dynamically changing view here so that no matter which file you're looking at, it
automatically filters by that particular project. So what do I mean by that? If
project. So what do I mean by that? If
you go back to our project template, like I mentioned, it's very nice to be able to use the base to just quickly add a new button and add all these properties in here. But templates
themselves are still a little bit more powerful. Bases are pretty cool because
powerful. Bases are pretty cool because we can not only create a base file in and of itself for project management, we can also embed that file here. So I can embed the project management base. And
what that does is it automatically pulls up the exact same base but within this file. So we can start to turn these
file. So we can start to turn these project templates, the epic templates, etc. into their own full-on dashboard.
But like I mentioned, we don't really need to see every single file of all of our project management system because what we're looking at here is a particular project. For example, I have
particular project. For example, I have my project of build an Obsidian plugin, something that I'm working on right now.
Maybe I also want to add my 100 days of writing project. So you can see as I'm
writing project. So you can see as I'm adding files to the base here, it gets added on the side here. But what would be nice would be rather than having this listed by every single view here or filter by tasks and then try and find
which project this relates to because you can see here it has multiple projects associated with it. What we can do is we can create what's called an embedded view. So this is where if we go
embedded view. So this is where if we go back to our main base here, I'm going to duplicate this view and I'm going to call it just project files. And what I'm going to do, we can see this was added as a new view on the top here, is I'm
going to introduce a filter only for this particular view where the project property contains and rather than putting in 100 days of writing or building an obsidian plugin, I'm going
to put this file. So you can see here it didn't really do anything, right?
Project files. There's no files in this.
But if we go back to the project template and I switch this to project files, what it's doing is it's using this filter where project contains this file as a dynamic element that's
referencing all of the files that have the project property filled with this note here pulling in the actual note name itself. So that's kind of cool
name itself. So that's kind of cool because what that means is we can add a specific view for project files, for epic files, stories, etc. It's all related to the file that you're
currently sitting in. So it becomes an embedded view and that's all well and good. But for
example, if we close this project template and we open it back up again, you can see that it just defaulted back to this entire base, not the project file specific view. So that's a little bit annoying. But there's a very easy
bit annoying. But there's a very easy way to fix this. In the same way that you can reference headings, you can reference views. So if I go over to this
reference views. So if I go over to this embed file here where I have this exclamation mark project management.base, I can put a number sign
management.base, I can put a number sign and it pulls up a list of all the views here. So now I can change this to
here. So now I can change this to project files. And what that means is
project files. And what that means is even if I go in and close this project template, if I go back to it again, it automatically keeps that particular view
as this embedded base. So that's a really powerful way where I can start turning this project template into a project dashboard template. And what I mean by that is if I go create, for example, go back to my build obsidian
plugin, I can just apply the project template here. And now what it will do
template here. And now what it will do is it will build in not only the base but specifically the base that relates to this project file. So now if I go
back to my all task table, if I click new and I call this use notebook LM to research building obsidian plugins and I make the project here build obsidian
plugin. Now if I go back to the build
plugin. Now if I go back to the build obsidian plugin dashboard, the project dashboard that note automatically appears in here as the kind. So we can do this for all of the views. I can go
to now project files and I will duplicate this view and call this project epics and I can add a new filter. So not only are we dealing with
filter. So not only are we dealing with the project contains this file, but we're going to add a filter of kind contains epic. And we're going to do
contains epic. And we're going to do this for each of those. So now what I've done is I've created an overarching project management system where I can see every single file that's within my
entire project management ecosystem filtered by projects, epics, stories, tasks, ideas, and bugs. And I've now built an embeddible view. So I can go back to my project template here on the
side and I can take this project files section here, this embeddible view, and I can duplicate it. And we'll call this project epics. And then I just need to
project epics. And then I just need to change this from project files to project epics. And you can see now it's
project epics. And you can see now it's embedding that particular view for this specific project of this project template project. And I can just do this
template project. And I can just do this for every single embedible view. So now
what's cool is if I go back to my build Obsidian plug-in template. Just going to clear this existing one for a moment.
And I now apply that template again, I now have all of those dashboard views automatically built into this particular project where it's automatically being filtered by this specific note itself.
So every single project view now gets its own dynamic ecosystem, which is pretty powerful because we basically just built one base that has all of these different views here where we can see our entire project management
ecosystem at a glance filtered however we want. And we can also click into any
we want. And we can also click into any of the particular project files, anything that has the kind of project like build obsidian plugin or my 100 days of writing and we can just quickly add in that project template and
everything will automatically be filtered.
So my guess is that in the future this new button will be able to pair it with a particular template where you could match for example kind equals this template. So if you're adding a specific
template. So if you're adding a specific view like task and you want to click the new button, it will recognize that you're dealing with a kind of task and then apply the task template. But we're
not quite there yet. I'm just guessing that that's something that they're going to bring in in the future.
So, now that we've taken a look and we've introduced all of these different views, we can also add a new type of view. And this is a new feature that I
view. And this is a new feature that I talked much more about in video two on the updates to Obsidian Bases on how you can introduce card views. But what we can do here is we can just duplicate this view. And this probably doesn't
this view. And this probably doesn't make sense for every single file in your entire system. So, I'm just going to
entire system. So, I'm just going to show you this for the all projects view for a second. And I can go here and I can duplicate this projects view. And
I'm going to call this all projects board. and I'm going to switch the
board. and I'm going to switch the layout to cards. So, this is where you can start to use bases in a much more visual way. And the way to do this is
visual way. And the way to do this is let's say I want to build this Obsidian plugin. What I can do is I can go down
plugin. What I can do is I can go down to the cover section and I'm going to take the Obsidian logo and I'm going to make this the cover image. So now if I
go back to the all projects board and I go to configure view, I can specifically choose the property I want to be the image. So I'm going to make this cover.
image. So I'm going to make this cover.
And by making it cover, you can see that the image just appeared right here. And
within properties, maybe I don't need to have all of this information here like parent or project. And I can simplify the view to be more visual. And you can see here I just added a new one for 100
days of writing using uh the image of code capture organizes still express but it doesn't fit here. So I can go to projects board configure view and I can actually control the card size here. So
that's kind of nice. And I can also choose the aspect ratio and whether it fits completely within the system. So
for example there I just switch it to contain. And now I've got this nice
contain. And now I've got this nice little cover image for 100 days of writing. So maybe this is the main view
writing. So maybe this is the main view that you want to look at as just an easy way to get an at a glance view of all the projects you're working on. So that
your project management base becomes this literal home base for you to just drop into, check out whatever project you're working on. I can click on the file and right away I get all of the
files organized within this particular project note.
And another thing is that let's say I'm dealing with very small to-dos. Well,
what I can do is in my project template, I'm just going to create an other notes section and I'll create a minor tasks section. So, if there's something that
section. So, if there's something that doesn't quite reach the level of being a full task, I can just keep track of it here. I can also have a related notes
here. I can also have a related notes section if I wanted to, which could be automatically programmed by the base as well, where I can introduce a function that checks to see which links are
related to this file. But I talk about that more in the Obsidian Bases update video. So I recommend checking that out
video. So I recommend checking that out if you want to see how you can apply more functions.
So I hope that helps you see how we're able to introduce all of this layered ecosystem through the basis views and the way that you're able to introduce functions and filters and start to
really turn your Obsidian vault into a database. And again, what I found very
database. And again, what I found very helpful for myself was starting this project management ecosystem with a new filter like kind or type rather than using tags because now I can start to
use tags on a more granular filter level rather than trying to use it to organize my project management ecosystem as a whole. So effectively what we've ended
whole. So effectively what we've ended up building here is a flowchart where you have a new idea and when you take a look at the idea in your inbox, you can say, "Oh, you know what? This is a really big idea. This is a new phase on
a project I'm working on." So you can convert that idea into an epic and then within that epic that'll give you a bunch of individual major tasks like stories that you can use within each
story you'll have a bunch of smaller tasks that you can introduce and then you go through and you action those tasks until you complete the story and then you've completed that story with the epic. So we have this ability to
the epic. So we have this ability to just start adding ideas to an inbox and then promote those ideas to wherever they are relevant within our task management ecosystem and we can just
work through the flow on a particular project. So effectively what we're doing
project. So effectively what we're doing is when you have a new idea and you add it to your table here by giving it the kind of idea you'll check to see is it a major idea then it's an epic is it a
feature or a story or perhaps one specific output like an article or a YouTube video then it would fit within the story category. If it's a single actionable step maybe it's a task. And
if it's a bug for something you're building then the idea would convert into a bug. So here are a couple specific examples. Now,
specific examples. Now, where for a YouTube my my overarching project is a YouTube series and maybe the epic within that is season 1 and within season 1 I'm going to have
multiple stories like produce an episode on Obsidian bases and then within that story of that singular episode I have a task of researching scripting recording and editing and as I go through and do
each of these tasks these individual tasks I will mark it as completed. And
that actually brings me back to one important component here where what we probably want to do is right now even if I mark a particular task for example as completed it still stays in this table
but we don't really want to have everything that's completed within this overarching table. So what we can do is
overarching table. So what we can do is we can go back to all project management files go to filter click back on all views and what we can do is we can add a new filter group or we can say where
status is not exactly completed and what that does is for example if we go to the build obsidian plugin let's say I've gone through and I have completed it if I change this to completed it gets
removed from the table.
So that just helps you key effectively create an archive because now what we can do this is where it starts to get even more powerful because I've created this filter and this particular filter is applied to all views within this
table. What I can do now is I can
table. What I can do now is I can duplicate this entire table and I can call this archived project management archive. And all I need to do to make
archive. And all I need to do to make this be the flip side of our project management system is go to filter all views and we just say is completed. So
now if I go through and I've finished building my Obsidian plugin and I want to change the status here to completed, it gets removed from the project management system and it gets added to my project management archive. So that
way you can keep track of everything that you have done and it has all of these exact views that are completely organized in the same way where it's just the reverse of our major filter at the beginning showing everything that's
completed versus everything that is not completed.
So for example, let's say I have my project which is my recalibrating blog.
That's going to be a many year project.
But within that project, I have epics that could be a series on project management. And within that epic series,
management. And within that epic series, I'm going to have individual articles like how to be agile in everyday life, how to use Cambban for writers. And
within each story, there's going to be a series of tasks like outline the article, write the draft, edit it, and then publish it. And within that ecosystem, if I ever have a new idea, I can just drop an idea into that project.
And then when I'm reviewing my ideas, I can figure out whether it fits into an epic, a story, or a task. So, it ends up being this really comprehensive and nice ecosystem that all flows really well together.
So, I hope this helps you see how you can use bases in a much more effective way for organizing your projects. The
fact that I'm able to just go to the all projects view and just click new and then that just automatically creates a file that goes into my projects view and then if I want to, I can just click on it and apply my template and everything
is organized automatically in a way that I know it's going to be filtered properly into my base. It's something
that I've been missing in Obsidian, the ability to control my files in a much more userfriendly way like this. So, I
think this is going to add a lot of power to Obsidian ecosystem as a whole.
So, my next plan is to go through and take some of the projects I've been working on, like I'm building an Obsidian plugin. I'm doing my 100 days
Obsidian plugin. I'm doing my 100 days of writing project, and I'm going to migrate all of my notes that are currently scattered or using data view into a way that they fit within this project management ecosystem so that I
can better keep track of what it is I'm trying to accomplish. So that completes phases one and two. Phase three, which is using AI to assist you with building and planning your bases. You can use AI
as a project manager.
I hope that this video helped you understand how you can start using the bases plugin in Obsidian, the core plugin, to actually manage your projects in Obsidian in a much more notion-like manner. A reminder to check out the what
manner. A reminder to check out the what is bases video if you're interested in learning more about how this tool will fit in with my bigger philosophy on how I see note-taking and AI working together. And also, I recommend checking
together. And also, I recommend checking out the most recent video that I made on the updates to Obsidian where I go through some of the features I talked about today in much more depth. If you
found this video helpful, I would love if you would please consider liking and subscribing. I'm working on making
subscribing. I'm working on making YouTube my full-time career, so any support is very much appreciated. A
reminder that I'll be making all of the bases that I built today as templates available for my paying YouTube members.
So, if you want to get access to these and not have to start from scratch with your project management system, please consider joining my paying membership.
If you want to go deeper into my overarching system in Obsidian and how I've been taking notes to build out my YouTube videos, write articles, and generally just do research, I recommend checking out my playlist on AI and Obsidian. And if you want to expand your
Obsidian. And if you want to expand your note-taking system even more if you want to get deeper into the research side and the writing side, I recommend checking out my videos on Obsidian and project management. I have a whole playlist. And
management. I have a whole playlist. And
I also have more templates available for my paying members getting more into what I call molecular zettocasten which is an atomic note-taking system that I've expanded into being a molecular one. I
think that this note-taking system the molecular zettocasting system is going to fit perfectly with the project management in Obsidian that's now enabled by basis. So I'm pretty excited to start tying these two together.
Thanks again for watching and I will see you in the next video.
Loading video analysis...