A Structured 8-Week Learning Guide for Mastering Tinderbox — Built on @satikusala's Video Series (253 Videos, Downloadable Tracker)

Q & A - getting started with Tinderbox
1

I’ve been working my way into Tinderbox and quickly realized that the learning materials are genuinely excellent — but navigating where to start and in what order is its own challenge. This post is my attempt to turn the existing video library into a structured, opinionated learning path for anyone who wants to go from beginner to confident Tinderbox user.

All credit for the content goes entirely to @satikusala (Dr. Michael Becker). His YouTube channel @drmichaeljbecker and the curated playlists he maintains alongside this community — including the invaluable Mastering Tinderbox: Training Videos (Complete List 1) and Complete List 2 — represent an extraordinary body of free, high-quality teaching. I’ve simply tried to give it a spine.

What I did

I pulled the full video catalogue directly from the YouTube channel and all four playlists using yt-dlp, cross-referenced and deduplicated everything, filtered out the non-Tinderbox content, and ended up with 253 TBX-relevant videos with real YouTube links and exact durations. I then organised them into a day-by-day learning plan targeting ~90 minutes per day over 8 weeks.

The result is a freely downloadable Excel tracker (link at the bottom) with four sheets:

  • Learning Plan — 40 days across 8 weeks, each day with a clickable YouTube link, a learning goal, and a status dropdown

  • All Videos (Complete) — all 253 videos sorted by category, each with a direct YouTube link and duration

  • PL1 – Learning Sequence — Becker’s original 204-video playlist in his curated order

  • Supplementary — 48 additional videos from PL2, PL4, and the channel that aren’t in the main playlist

The 8-Week Learning Path

The core philosophy: one topic focus per day, no date pressure, practice days built in. Every week includes at least one “practice day” — no new video, just time to build something in your own TBX file. Learning science is pretty clear that consolidation time matters more than raw input volume.

Week Focus What you’ll build
1 Fundamentals — interface, prototypes, attributes, agents A working TBX file with prototypes, attributes, and your first agent
2 Notes manipulation — media, exploding, linking, Action Code basics Explode workflow, OnAdd automation, first Display Expression
3 Export & Publishing — templates, Markdown, Pandoc, CSS, blogging A working export template and a simple Markdown publishing pipeline
4 Practical use cases — Daily Journal, Gradebook, working sessions A personal Daily Journal template
5 Advanced Action Code — Regex, Taggers, Glossaries, Nested Lists A tagger and/or automated glossary agent
6 5Cs Knowledge Management framework Your own 5Cs workspace structure
7 External integrations + selected meetups (Zotero, Obsidian, Anki, DEVONthink) Research workflow connected to TBX
8 Current meetups — AI, MCP/Claude, Git, Information City (TBX 11) Reflect on your system, set next goals

Sample Week 1 in detail

Day Topic Videos ~Min
1 Interface & first notes V01 Intro · V02 Toolbars · V03 Creating your first notes 22
2 Prototypes, Attributes & Inheritance V04 Prototypes · V05 Attributes · V50 Inheritance 62
3 Agents I — Queries, Actions, Rules, Edicts V06 · V07 · V08 24
4 Stamps & Adornments V09 Stamps · V15 Agent Designator · V16 Adornments 30
5 Practice day — no video Build your first complete TBX file from scratch —

A few things I noticed along the way

The PL1 playlist is already a curated sequence. Becker arranged it deliberately — it starts with the 2-minute intro and builds systematically through to the most recent meetups. If you want one canonical path, just work through that playlistin order. The learning plan in the tracker is my interpretation of that sequence, chunked into digestible daily sessions.

The meetup recordings are a different kind of resource. The structured training videos (roughly the first 60 entries in PL1) are dense and efficient — most run 5–30 minutes. The meetup recordings run 90+ minutes and are more exploratory and conversational. I’ve placed them in Weeks 7–8, after the foundations are solid, because they’re much more valuable once you have enough context to follow the discussion.

253, not 274. The channel has 274 videos, but about 17 are non-TBX content from Becker’s broader work in identity and mobile marketing, plus a handful of deleted/private entries. Everything TBX-relevant is included in the tracker.

6 Likes
2

Fascinating!

Things that might also be useful:

• a Tinderbox document that provides a structured overview of this material
• a topical guide to Tinderbox meetups on YouTube and Vimeo
• a survey of tricky topics or FAQs

5 Likes
3

In my ‘hat’ as aTbref’s author I’m also interested by what’s hard to find (long-time users may overlook its search) or parts of a topic that aren’t well (enough) cross-linked.

Had I known, 20+ years back, the the resource would run this long I might have structured the source TBX differently (aTbRef is a static page website that reflects the source TB’s outline). But so many features turn up in more than one role and we have forms of use today we didn’t have then. So, it’s easy fro me to call the old design sub-par, yet what would be better structure—for all users, not just ourself. Still, input on things I can easily fix, like new cross-links or terminology association (i.e. what some call an ‘X’ is a ‘Y’ for others), is genuinely welcomed as the resource is written for others, not myself†.

†. In its early days it was written to help me understand Tinderbox. But the point of the website it became was to share the info with others. Now, I don’t think anyone—apart from some stalwart beta testers—use every feature of Tinderbox’s rich toolbox. So there are always less visited corners of the toolshed which nonetheless will be of crucial importance to some users.

1 Like
4

Thanks! Very helpful. I’ve struggled mighty to give our work here the “spine” that it needs. :slight_smile: This is great. I’ve run several Tinderbox teaching cohort, as well as teach in other context…the challenge i’ve found is that it takes a lot longer than one might expect to “teach” this material, and preparing the material in the first place text 6 to 10 yours for every hour of material (more when it is on-demand videos).

1 Like
5

Writing from my perspective as a 23-year-old user:

I am probably one of the youngest users in this community. Objectively, this may not matter much — but I think it gives me a unique vantage point to speak on behalf of my generation.

Note-taking, thinking, and learning are just as relevant today as they were two decades ago, and they always will be. I’ve lost count of how many new note-taking and productivity apps are released every day. These apps — Notion being a prime example — promise a clear vision of what you can expect when you invest your time and money into them. They onboard you within minutes, offer ready-made templates, and give you an immediate sense of productivity. Young people grow up with exactly this kind of experience, on mobile-first devices like smartphones and iPads, where instant feedback is the standard.

As a young adult at university, I receive an overwhelming amount of new information every day — filling up my physical notebook, iPad notes, my head, and a growing collection of documents. Most people, I imagine, are not willing to spend weeks experimenting with a tool unless they can clearly see what benefit it will bring them. And when they evaluate a new app, they inevitably compare it to everything they already know.

That was precisely my situation when I first encountered Tinderbox. I was looking for a great application to capture, manage, and connect my notes — one that wasn’t subscription-based. The features looked compelling, the pricing was fair, and the long development history signalled a proven, mature piece of software. I appreciate minimalist, functional UIs, and Tinderbox seemed to tick every box.

But I had no concrete sense of what to expect from it for my personal use case. And that, I think, is the heart of the problem.

I started by watching Michael Becker’s introductory videos, built a few small test projects, and grasped the basics within a couple of days. Yet it still felt like an elaborate mind-mapping tool with attributes attached to notes — something I had just paid over $200 for, but that didn’t feel as intuitive as Obsidian, Bear, or Notion, which I already knew. I wasn’t as impressed as I’d hoped. More importantly: I didn’t know where to meaningfully start.

Here is what I now understand, but didn’t at the time: the learning curve in Tinderbox is not primarily technical — it is conceptual. Most tools give you a system. Tinderbox gives you a set of instruments and leaves the composition entirely up to you. Coming from apps that offer ready-made templates and guided setups, this open canvas felt more like a barrier than a feature. The manual even states openly that you don’t need to get the structure right at first — but when you’re new, that kind of freedom is disorienting rather than liberating.

I also came in with the wrong expectation entirely. I was looking for a finished system — something I could slot into my existing workflow immediately. What Tinderbox actually offers is a tool, not a system. That distinction sounds small, but it fundamentally changes how you need to approach it. No amount of documentation prepared me for that shift in mindset.

What eventually helped was abandoning abstract experimentation and focusing on one concrete, real problem I actually had. Only then did Tinderbox start to make sense. But I had to discover that on my own — and I suspect many young users give up before reaching that point, simply because they never receive that guidance upfront.

And there is one more thing worth mentioning: Tinderbox’s greatest strength — that structure emerges naturally over time, shaped by your own thinking — is also its hardest quality to communicate. That kind of payoff reveals itself over weeks and months, not hours. Young users today often decide within the first few sessions whether a tool works for them. If the value of Tinderbox only becomes tangible after sustained use, then bridging that gap has to be part of how it is introduced.

That said, Tinderbox is a genuinely great application, and I say this with full conviction:

  • Not subscription-based

  • Runs entirely locally

  • Over two decades of development, documentation, and refinement

  • An exceptionally supportive and knowledgeable community

  • Rich learning resources: forum posts, books, Michael Becker’s YouTube content, and regular meetups

  • It does not think for you — it is a tool in the truest sense, with no AI-driven shortcuts that replace your own reasoning

  • Fully modular and unrestricted — no forced structure, no imposed workflow, no artificial complexity

Honestly, I believe young people are missing out on this remarkable piece of software — not because it isn’t good enough, but because they cannot get a clear picture of what to expect from it, and when to expect it. That is a shame, because students and young adults are precisely the people who are actively studying, thinking, and learning right now — and who stand to benefit the most from a tool that grows with them.

I don’t write this as a criticism. I write it because I genuinely believe in what Tinderbox is, and because I’d like to see more people my age find their way to it.

6 Likes
6

Tinderbox absolutely has its place. But I think it’s worth acknowledging the reality that many young adults are operating under right now.

We live in a time where everything moves and develops at an extraordinary pace — and with that comes a quiet but persistent pressure to keep up. People expect us to be efficient with everything: our studies, our output, our tools. The implicit standard is maximum results at minimum time, cost, and effort.

That is probably a large part of why applications like Notion are so popular in my generation. They use smart automation and AI to eliminate repetitive work — importing information, formatting notes, applying templates. For someone without a strong background in coding or automation, these things just work, out of the box, immediately. And in an environment where efficiency is expected as a baseline, that matters enormously.

To be clear: I personally have no interest in AI features that summarize articles or generate ideas on my behalf. That kind of thinking is mine — I want to keep it that way. But I would absolutely embrace automation when it comes to the tedious, mechanical parts of a workflow: moving information between apps, structuring existing notes, handling repetitive formatting. That is not outsourcing thinking. That is just removing friction.

And friction is exactly where Tinderbox loses people early on — and it hits harder than it might seem from the outside.

It is worth being honest about the financial dimension too. Notion is free. Obsidian is free. Bear costs a few euros a year. Tinderbox is a serious upfront investment, plus annual upgrade costs. For a 23-year-old, that changes the risk calculation entirely. If the tool does not click quickly, you are not just left with lost time — you are left with lost money and a quiet sense of having made the wrong call. That psychological pressure to see a return fast is real, and it shapes how much patience a young user is realistically able to bring to the onboarding process.

And the onboarding process asks for a lot. Without a solid foundation of Tinderbox knowledge, getting your existing information into the tool — your notes, documents, and thoughts scattered across other apps — is an enormous amount of manual work. Every other major PKM tool addresses this directly: Notion has mass import, Obsidian reads plain Markdown, both offer browser clippers and migration paths. Tinderbox’s more open approach to importing fits its philosophy, but for someone arriving with an established system, it creates a gap that is genuinely hard to cross. I don’t say this as a criticism of the philosophy — I say it because it is one of the most concrete points where young users stall.

The deeper issue, though, is not financial or technical. It is cognitive. As a student, my mental bandwidth is already stretched thin on any given day. If a tool costs more energy during the learning phase than it returns, the rational response is to set it aside — regardless of how powerful it might become over time. That is not a failure of patience or commitment. It is a natural response to an onboarding experience that has no clearly defined entry point.

That is perhaps the most honest way I can put it: there is no “Tinderbox in 30 minutes” experience. Apps like Notion or Bear have a core concept that reveals itself within half an hour of use. Tinderbox deliberately does not — and I understand why. But I think what is missing is a single, minimal, clearly scoped starting path that delivers one genuine success experience early on. Not a tutorial. Not a manual. A real, concrete problem, solved, in a short sitting. That first moment of “this is why I’m here” is what makes everything else worth learning.

I love the underlying concept of Tinderbox deeply. I often think of it the way I think of pen and paper: a set of fundamental instruments that can be as simple or as sophisticated as the situation demands, with no ceiling and no forced structure. That philosophy resonates with me completely.

But right now, starting with Tinderbox can feel like being handed a pen and a blank sheet — and being asked to rewrite every document you’ve ever owned by hand, from scratch, before you can begin the actual work. Closing that gap, even partially, would change everything for users like me.

Hope this can give some insight in the struggles with getting started using Tinderbox nowadays! (:

6 Likes
7

One of the things that genuinely impressed me about Tinderbox is its community. It is active, knowledgeable, and clearly built over years of shared investment in the software. The regular meetups, the forum, the depth of discussion — that kind of sustained engagement is rare. Most apps never come close to fostering anything like it.

And it is obvious that this is a living ecosystem. The software keeps developing, the people who have been here for years keep pushing it further, and their projects grow in complexity alongside their expertise. That continuity is something to be proud of.

But seen from the outside, as a new user, that same continuity can feel quietly intimidating.

When I browse the forum or watch meetup recordings, I see people working on problems I am not even close to thinking about yet. User’s talk about the latest Claude implementations, while I’m not even halfway done reading “The Tinderbox Way”. :sweat_smile:

The technical depth is genuinely impressive — but it is not relatable to someone who is still trying to figure out how to get their existing notes into Tinderbox in a way that makes sense. The gap between where the community is and where a beginner starts is not just a learning curve. It is a difference in entire mental models.

What is missing, I think, is a visible path for smaller, more beginner-friendly projects — a clearer “this is where you start” that sits alongside the more advanced work, rather than being overshadowed by it. Not because the advanced content is wrong to share, but because right now the signal a new user receives is: everyone here is already far ahead, and I don’t yet have a problem worth bringing.

The community is one of Tinderbox’s greatest strengths. Making it feel accessible to people at the very beginning of their journey — people who haven’t yet built anything complex, but who are genuinely curious — would make it an even more powerful one.

That’s why I thought some sort of organized and chronological getting started guide would be helpful for most users and make the usage of Tinderbox future proof for the next generations. (:

6 Likes
8

This is a superb contribution - very well done, Niklas, and thanks for the structured way in which you’ve presented it. I’ve been a TB “user” (and I use that term very loosely) for many years, but I always seem to have trouble understanding the basics. And yes, all credit to Dr. Michael Becker for creating the very watchable YouTube content.

I think your contribution is the missing link, and it’ll help new and established users alike across the TB community.

1 Like
9

Well done, Niklas! A great contribution to the Tinderbox community!

1 Like
10

Love your analsyis. BTW, have you seen these templates/frameworks, you may find them helpful: 5Cs of Knowledge Management (especially the FREE ones).

1 Like
11

Thank You, yes I already saw these! Great resources (:

1 Like
12

Could you kindly double-check whether die dropbox-link is working properly @nkoenig as i see an error message telling me that the .xlsx cannot be opened.

thank you

13

No Problem. The link works fine, there‘s just no preview on mobile devices as it seems.

14

I confirm the download link works. This message below, as @nkoenig suggests relates to previewing the file. Clicking the download button, regardless and it works.

TBX_Complete_EN.xlsx 2026-04-21 08-03-04
TBX_Complete_EN.xlsx 2026-04-21 08-03-041330×612 66.1 KB

Tip: if using Dropbox links, change the 0 (zero) at the end of the link to a 1 and the link doesn’t open the Dropbox site and simply downloads the file (via the web browser). I do this as it is less confusing for the recipient of the link: click the link, get a file. I can see the Dropbox’s marketing department would prefer you see their website so they have an opportunity to sell their service.

2 Likes
15

Yes, I get the same. Tried multiple times but all I can download is a file that is 112 bytes (not KB, just B) and nothing will open it.

16

No Problem, here‘s an alternative link for google drive: Loading Google Sheets

1 Like
17

Yes, I also tried using modified link https://www.dropbox.com/scl/fi/rnrpxe1hpd2bxj0f1byjj/TBX_Complete_EN.xlsx?rlkey=fvnh7n3rj87qe27pc9voqe8ar&st=mpmevj0p&dl=1 as per tip above. File download but is 112 bytes.

So it lookalike the source file is wrong in some way. IOW, the link works, but what the link fetches is not a complete file.

19

I‘ll fix the file and reupload today. Sorry about that

1 Like
20

TBX_Complete_EN.xlsx.zip (70.0 KB)

Here is a zipped Version of the working file!

4 Likes
21

No worries. Thanks for the attention.