A bunch of years ago, my wife signed us up for a plot in the local community garden. We didn’t have much room in our yard for any kind of real gardening, so the community garden was the perfect solution for us. Well, for her mainly, since she’s the green thumb in the family.

We’d go down every weekend for a couple hours to do some weeding and check on how our plants were doing. I don’t even remember what we planted, likely just a mix of vegetables. But it was fun.

My son especially loved it. He would run around and look at all the little garden plots, flying up and down the pathways amongst the boxed plots. And then he would come back and tell us all the things he saw that other people were growing. Then he’d play in the dirt with us for a bit before heading home.

I feel like that was me today, running up and down the internet’s garden paths, looking at all the awesome things other people were growing in their little (and sometimes not so little) digital garden boxes. As lovely as they all were, though, I still couldn’t quite find something that matched what I wanted to do.

My main problem, I think, was in the starting conditions I’d given myself. As I think I’ve mentioned before, I’m currently testing two different platforms in this blogging experiment. I mirror all my posts between two sites, one run on WordPress, and the other run on Micro.blog. These have both been great so far for putting up posts with ease. And when combined with MarsEdit, the friction factor is reduced to near zero for me. I just sit down, type, and publish. Easy peasy.

And since it felt so easy, I had decided early on that I would like to try and make the digital garden using WordPress and Micro.blog as well. At least try, and see if either one worked better than the other, or if either worked at all.

But I kept running into the issue I described yesterday, where I was worried I’d end up with a mess of individual pages with no real organizational structure to help me keep track of them all. I don’t have any strong methodology behind how I take and make notes, so I knew I’d need some kind of structure to help me keep things organized. It just wasn’t looking to me like these platforms would fit the bill.

So today I expanded my search a bit wider. I went back to my initial restriction, using only WordPress and Micro.blog, and decided that might not be the best way to move forward. Then I stepped back a bit further and started thinking about what I wanted this garden to even be. The more I thought about it, the more I realized that it wasn’t going to be any kind of extension of these blogs. Instead, it was going to be its own thing, and it needed to be treated as such.

This was when I came to two important conclusions.

Firstly, I realized I’d need to set up a new subdomain to run this project on. Not only would this help from an organized mindset for me personally, but it would also allow me to develop something independent of the blogging platforms. And it would also give me flexibility down the road if/when I need to make any changes on what I’m using for the backend.

Secondly, I realized that I needed a dedicated environment to write and publish garden entries. I’d been fighting this idea initially, but the more I thought about it, the more sense it made. The moment I accepted this, I knew it would be the right move.

So back to the research I went, looking through what I’d collected so far for reading material on the topic of digital gardens. I re-read everything, spending more time looking closely at the software tools that others were using and recommending. And that’s when I came across this little gem from Maggie Appleton’s post on Digital Gardening for Non-Technical Folks:

“Overall, Obsidian is a great option for anyone who wants to keep their garden simple, non-technical, and get up and running quickly."

Hey, look! That’s me she’s just described!

I’ve used Obsidian a bit, but I’ve never played around with its Publish feature. Mainly I’d been using it for its Canvas feature, which I loved. But then Apple launched the Freeform app which provided similar functions, so I started trying that out. And while I found Freeform to be more restrictive and less versatile when compared to Obsidian’s Canvas, I had to admit that the learning curve wasn’t quite as steep with Freeform.

But now I have a great reason to dive back into Obsidian. Because I think this just might do the trick for me. So that will be the next step. Dive back into Obsidian and see if this will do the trick for me.