This time of year sees me reflecting on the past season and thinking about how to make things better. Lately I’ve been working on upgrading the backend of our programs. Our portfolio system requires students to document a lot of things when they’re on a course with us, and it has gone through a long list of upgrades and changes over the years. A while back we used paper-based student portfolios. These were great, but they would get wet, get lost, have pages go missing – it was a challenging system for an outdoor education program. So one winter I wrote everything up in Google Docs. I set up a Google classroom to manage and track everything, and it worked OK for a while. Eventually, though, challenges with permissions and access increased my frustration levels enough to drive me away.
To avoid Google Classroom, I created a homebrewed hybrid classroom that contained two parts: our outward facing classroom as part of our online community via Mighty Networks, and all of the workbooks and documentation in word files and updated via PCloud, which is similar to Google Drive but with a lot less bullshit (my opinion). And this has worked for a few years. The formatting of the word files has been a thorn in my side, as trying to create workbooks that work on any platform, on any device has been challenging at best. And maybe it’s just me but most corporate software seems increasingly enshittified. I’ve been personally eliminating said corporate software from my workflows wherever possible, and have been on a markdown kick for two years and counting. These days I do all of my digital writing, from shopping lists to blog posts to website updates, in markdown.
So my challenge this fall has been to migrate all of our course documentation from word files to markdown. I’ve spent the last few weeks putting myself through a crash course in Obsidian, and have got the bulk of the student portfolio templates moved over. I’ve developed a shallow working knowledge, but it’s deep enough for me to do the basics, which is all I need at this stage.
My experience thus far has been extremely positive. My goal has been to keep things as simple as possible, so migrating from using tables in a word processor for collecting data has been replaced with plain text data collection, but I like it. It will be an adjustment for sure, but in the long run I know the more friction I can remove from the documentation side of our programs, the more likely people will complete it.
I’ve been testing it on different devices, and data collection and merging has worked flawlessly. If you’re tech-saavy this might sound like someone getting excited about the invention of the wheel, but for me (and many of our students), this is a big deal. It takes away friction and makes daily documentation more likely to be completed.
In addition to our use case, there are a lot of good arguments to be made for switching to markdown. It is simple, future-proof, portable, works offline, and is privacy-first. If you are new to it, here are two essays that explain it clearly and concisely.
– File Over App – https://stephango.com/file-over-app
– Markdown Files, Not Apps – https://andrewstiefel.com/markdown-files-not-apps/
For the next year or so I plan to maintain the old student portfolio written in Word as well as the new one written in markdown using Obsidian. And as a backup, I’ve got the whole thing saved in a printable pdf format. So I seemingly have the bases covered.
If you think this is a whole lot of nerdy nothingness, you wouldn’t be wrong. It’s not the sexy side of running a bushcraft business by any stretch. But I’m always trying to look forward, not backward. This is where I see things going for us.






