Jean-Charles Noirot Ferrand - Friday, August 29th, 2025
Disclaimer: The content of this blog post is my own approach on Obsidian which is constantly evolving as I spend more time on Obsidian. While I believe some pieces here can be applied to any Obsidian vault, I strongly suggest exploring it yourself.
Before explaining my setup, what is Obsidian? Obsidian is a knowledge management/note-taking akin to Notion. The idea is that every file within the vault (aside from attachments) is in Markdown. The great thing about Obsidian is the amount of customization. You can essentially change everything about your experience, whether it is the appearance (through Themes or CSS Snippets) or the functionality (with Plugins). I started using Obsidian in Summer 2024, and it has been very helpful for my daily work. I use it to track and manage tasks, archive notes on papers, take meeting notes, write reviews, and more.
A skeleton of my vault is publicly available at this GitHub repository. It includes a selected subset of the directory tree, templates, and the plugins, themes and CSS snippets I use.
I organize my vault around three main directories. The main rationale is to keep things related together and separate work/life/maintenance:
RESEARCH
CODE
(also used for artifact reviews)LOGISTICS
MEETING
READING
(papers or reviews)WRITING
(papers, reports, guides)PERSONAL
ADMIN
BLOG POSTS
(you’re reading one!)DIARY
(archives random thoughts for later expansion in THOUGHTS
)MISC
(notes vital for vault functionality, templates, attachments)
ATTACHMENTS
(images, embeds; change the “Attachment folder path” to this folder)BASES
(Obsidian 1.9.0+ plugin for database){DAILY,WEEKLY} NOTES
EXCALIDRAW
(plugin-related files)MOC
(Map of Content; may be outdated due to Bases)PEOPLE
(one note per frequent contact, useful for meetings)TEMPLATES
Obsidian allows you to tag your notes. This allows a better organization and certain operations like filtering. However, it can become overwhelming when you don’t keep track of tags. To this end, I developed my own tags taxonomy (under a note brilliantly called TAGSONOMY
). The core idea is to separate the tags into multiple sets similar to the vault structure (WORK/RESEARCH, PERSONAL, MISC).
My homepage looks like this:
Aside from the aesthetic (banner and graph), it is made of three elements:
Some people prefer having the homepage serving as a hub to navigate other notes, but I found it redundant for my use case (I don’t spend that much time there).
My daily notes are pretty straightforward (quick access to note creation, tasks, scratchpad). I also show notes created/edited during this day. Here’s an example:
Weekly notes are where I prepare for the upcoming week. Under the “Main Objectives” section, I fill in all the tasks for the week. The view below per day shows where the tasks are scheduled in the week.
The Tasks plugin is among my most used plugins. Every Sunday, I create a new weekly note (if not already created) and list all tasks for the week, grouped by project or type.
For each task, I do the following:
due date
(if applicable)schedule date
priority
TASKS
tags such as Depth and TypeTip: Making the task name self-contained avoids confusion when juggling multiple projects.
You’ll find more details on the tasks plugin here.
My vault comes with a few themes I like, but I mostly converged on the Blue Topaz theme as it comes with many settings.
I use the following CSS snippets:
To make my experience more visually appealing, I use a few plugins which I briefly detail here:
I use a fairly wide array of plugins to manage my vault:
While it provides a pretty good UI, some hotkeys can be pretty handy . Below is a list of hotkeys that I use fairly often, excluding the usual text editing ones.
Ctrl + O
: Quick select a noteAlt + H
: Navigate to HomepageAlt + T
: Edit selected taskAlt + ← / →
: Navigate Daily NotesAlt + D / W
: Daily/Weekly noteAlt + 1…6
: Set markdown headingCtrl + Shift + F
: Search all filesCtrl (+ Shift) + E
: Switch viewsThere are many options to back up and sync your vault. I currently use two of them:
Bonus: I back up a public subset of my vault automatically to a GitHub repository with a bash script.
There exists other options you might want to take a look at:
Sometimes, I realize that a template I’ve been using could be improved in some way and while fixing it would improve newer notes created from it, it would not fix the notes already created. For example, I used to hard code the Meta Bind button in my Daily Note template, but when I found that I could just implement them once and reference them in the template, I changed all my previous Daily Notes (about 200 at the time). Instead of doing that, I use VS Code which is pretty handy when it comes to mass refactoring (search and replace all files with Ctrl + Shift + F).