Table of Contents
Iāve finally got my blog posts organised within Obsidian. Hereās how I did it.
Prior to this week, my blog posts in Obsidian were floating around in the ether that was the āBLOGā folder. Published and unpublished mingled, and I didnāt really know what I was working on, nor what I should be working on. Combine that with; lists of ideas in various physical notebooks, several notes with lists of blog ideas, and two blogs which each had 10ā20 ādraftā articles, and you can realise the need for some more structure!
What I needed was a blog pipeline.
(I really donāt know how you people with no folders whatsoever manage to survive; kudos š¤£)
My Blog Pipeline Requirements
I didnāt want this pipeline to be overcomplicated. It needed to be an efficient use of time and resources. My 5am brain takes a little while to get up to speed and I didnāt want complex YAML getting in the way. We all know that Obsidian can both be a wonderful note-taking and note-making tool, but it can also take us on a deep journey, where optimisation and integration are key and everything must be perfect! Well itās never going to be perfect, so I was aiming for āit just worksā, āit does what I needā and āitās easyā. But I also wanted something a little bit beyond base Obsidian functions.
Obsidian Projects Was My Plugin of Choice
Iāve wanted to really make use of Obsidian Projects ever since it came out. It doesnāt currently work well with my current research work setup without some major tweaking of notes. Therefore, Iāve been on the lookout for the perfect āprojectā to use with it. My need for a blog pipeline seemed like the perfect opportunity to try it out.
Also Read: Three Essential Obsidian Community Plugins My PhD Couldnāt Do Without
First Steps of Getting Things Organised
Firstly I spent some time getting all published and unpublished blogs into the appropriate separate folders. At this stage, Iām keeping published ones separate, because they are finished. In my physical and digital life, I find putting things out of sight really helpful in keeping focus. Once blogs are published, I donāt need to see them anymore. Any tweaking, up-dating etc. will take place on the blog on which they are published. I might make a note that Iāve made an update, but the reality is they wonāt be touched again. They may be referenced to in a future post as I reuse and rejig content as new ideas come in, but keeping them compartmentalised somewhere else helps me keep my work surfaces tidier!
I also realised that I needed another folder for another type of content. I have called this my āIDEAS POOLā, kind of like a swimming pool of ideas, to be dipped into when I want to get inspiration. These are unformed ideas, where there is a concept, but Iām not sure of what it is that I actually want to say. In the context of this post it would be the difference between āBlog Organisation Optionsā and āHow To Use Obsidian Projects To Create A Blog Pipelineāāāāsee the difference? One note I have in there at the moment, is rather unhelpfully called āProcrastinationā. I know what that note is about, but itās pretty useless when it comes to writing something more structured. I guess what Iām trying to say is that I need a post title for it to make it into the unpublished ideas folder.
As I went through drafts in my blogs I also realised that I needed an archives folder. These are posts I wrote for previous blog iterations and I no longer want to have published. I donāt want to delete them completely, but they arenāt particularly useful at this stage.
Finally I have a separate note in the main blog folder called āBlog Article Idea Dumpā as a collection point for on the go ideas. On writing this, I realise I need a better name than āDumpā⦠suggestions welcome! I also have the tag #thingsofnote/blogidea which I add to a note if Iām in the middle of something else and donāt want to stray into the ether.
So, after finishing this step, I now have four folders; IDEAS POOL, UNPUBLISHED, PUBLISHED and ARCHIVE, along with an ideas list and a quick tag. The pipeline has begun! But I wanted to go further. I wanted to have stages and clear next steps within UNPUBLISHED. Now it was time to call on the āProjectsā plugin.
Enter the Projects Plugin
I already had it installed so it was just a case of hitting āCtrlā +āpā to set up a new project. I watched āObsidian for Content Creators (ft. Projects Plugin)ā by Sergio as a super straightforward guide to remind myself how it all worked. It was Nicole van der Hoeven] (<- awesome YouTube channel and person) who first opened my eyes to the Projects plugin. Canāt remember which video it was specifically, so Iāve just linked to her general channel because she is so good š.
I had a little play about to see how it worked before starting to allocate my unpublished posts. I like to have a play about to see what a system can do before jumping in, just in case there is a key function I need missing. I started in Table view because that was the logical step, but I soon found myself switching to the Kanban āboardā option.

- Tableāāāarrange files in a table, easily sorting by a-z or z-a
- Boardāāāarrange files according to a chosen YAML parameter
- Galleryāāāview according to chosen āimageā parameter
- Calendarāāāview according to a date parameter
I like how adding a YAML option in one note in the project folder also adds it as an option to all the other notes. It makes it super easy to add parameters and options in as needed. Itās also super easy to add a new note (i.e. a new blog title) onto the board Status. I also like how we can change the visual view of how things are organised and focus or filter what we can see in the different views at any one time. This flexible system is what makes Notion popular. Although ironically it also what made me not like Notion!! Notion seemed to get so complex, so quickly; āassigningā things into an ever-changing table seemed to take up most of my time. There was always some other level of detail that I could add. Sometimes having similar functionality but at a basic level (i.e. the plugin isnāt super complex at this early stage) is actually better.
(Note: I do use Notion for organising my garden, because it seems to suit āplanningā and ātask managementā a lot better, but Iām still having issues with the cascading complexity of database tables⦠but maybe thatās just a me problem š¤)
Optimising the YAML for Obsidian Projects
As I mentioned before, I wanted the pipeline and the YAML to be super simple and non-taxing i.e. obvious. I donāt want to have to remember which options it could be. After a bit of trial and error I went with the following:
- name; the note (blog) title
- status; concept, outline, writing, editing, images -> i decided against having a āresearchā option because it is so interwoven into the way I write posts, it doesnāt really have a specific stage. Plus some donāt even have a research stage. - todo; a few words outlining the next step such as ācreate a frameworkā, āmake a table ofā¦ā or āresearch ā¦ā. The most important thing about this one is that there is only *one* ātodoā. Itās a trigger so I know where Iām at, rather than a list of everything that needs to be done (because that would never end)!!
- publication; which blog to post on, at the moment only three options
- priority; to identify which posts to work on first
I also decided against a ādeadlineā or āpublish byā type options for the time being. My blogging and writing is still very much a passion project so I donāt want hard deadlines. Iād probably just ignore them anyway! I do love this feature of projects though and it may be one I use in future.

Challenges of Setting Things Up
It also took me a little while to get to grips with the finer points of Projects. For example, whereas Dataview will see āTitle: ā and āTitle::ā and āTitle :ā YAML as the same (at least I think it does, Iām definitely not an expert here š), projects does not. Thatās the problem I have with integrating it with writing for my PhD; it allocates the title YAML under three different columnsā¦
Projects doesnāt like capitals much to be honest, once you want to create a board view. But in a way thatās nice; no capitals is simple. A little ugly, but simple.
(On a side-note with the Title: , Title::, Title : and title: problem, the Linter plugin should hopefully be perfect for sorting this out, but I digressā¦)
It did take me a little while to put these together and to sort out all posts, but thatās not a projects issue, thatās a me transitioning from disorganised to organised issue. I also, as of writing this, have not gone through all my notebooks to add in what I have in those. I do a lot of my more creative writing manually, so Iām super excited to eventually get everything together.
My next challenge, and who doesnāt love a challenge, is to get all my book writing together. Iām wondering whether Projects would also work for this or whether something more akin to the āLongformā plugin would be better? Please leave thoughts and suggestions below!
The (Current) Finished Blogging Pipeline
My finished pipeline isnāt at all complicated, although this post may make it sound like such! What matters to me is that I have a clear place to put new ideas and how those ideas progress to the finished āthingā.
If we start from the āidea popping into my head but now is not convenient to elaborate or allocate stageā, Iāll just open the daily note, note my thoughts, add the #thingsofnote/blogidea tag and continue with my day. If weāre at the āIām up for some Obsidian optimisationā then Iāll delve into the tag or ideas dump and allocate the ideas to the pool or the concepts option in the unpublished folder. If Iām in the āI have so many ideas right nowā then Iāll open up my ideas dump and fire away. Most importantly, I can wake up at 5am, pre-coffee and know exactly what needs doing. If Iām feeling like writing, I can pick something from there, whilst easily identifying which have the highest priority. If I fancy taking photos, I can easily see which posts need images, or if editing is my jam, Iāve got posts ready and waiting.
And there you have it! Itās a super simple and efficient way for me to know what I need to work on.
And if you want a more general nosy around my vault: Go for an Obsidian Vault Tour
How I Might Improve or Change the Pipeline in Future
If blogging becomes less of a hobby and more of a business, it is likely I will make more use of the dates and calendar function. Itās exciting that the option is there. The other thing I might add in, which is a nod to the āMind Management, Not Time Managementā way of things, is a status to identify what āmental stateā the post needs. Butā¦I think it would be more useful to do this more generally in an MOC-sign-posting-style note. A sort of, āif thisā then ādo something like thisā kind of note.
(As an additional note, as I finalise this for publishing, it would also be useful to have a Medium ātagsā list!)
Itās likely that this plugin will develop lots more functionality in the future so it will be exciting to follow along. For now, I like its simplicity, if Iām going to be honest. Projects is currently uncomplicated and limited in its functions, but still powerful in its use and thatās what makes it work for me.
My Suggestions for Plugin Improvements
Iām sure Marcus (the developer) has a list of improvements as long as his arm. For what itās worth, this is a great plugin at the moment, but it has the potential to be amazingly powerful. I suspect most of what I have listed below is already on request. Some of my suggestions from my first forays are:
- allowing other views to work with field with capitals
- colour complete boards and rows, not just coloured icons
- allow notes to be moved from one board to another in board view
- having an option to remove the field name from the board, so you see just the contents of the field
- have different coloured tags/attributes
- allowing columns to be moved around in tables view
- enabling āenterā to be pressed when using the āedit noteā function
- more complex sorting options
But if nothing changes, I donāt mind. It does exactly what I need without bells and whistles, and for that I am extremely grateful. Iād love to see how others have used this plugin; feel free to leave a link down below and Iāll come for a looksie.

Comments