I would be honoured! I love honest conversations about the good/bad/ugly :D

We also use several status properties for different parts of episodes, so assets can have a status, while the recording itself can have its own status, etc: Then we have different views to help us see what's missing (cover images, etc). SO I personally lean toward more being done via properties

I do sometimes use a combination of both: some simple checkboxes in the template, others as "tasks" in the task database, and others as more advanced status properties, etc. No right/wrong way, but worth checking in on where there's friction currently in your process.

"It depends" :D Checkboxes in a page = super easy, low effort. However, it can be really easy to "miss" what work still needs to be done, or get a true idea of capacity when you've got multiple projects/episodes on the go. Some of this could be part of a status property, some could be in the body:

@kaidav.is is a wildly generous person :)

Why indeed... www.independent.co.uk/news/health/...

Got this gem today

Maybe @kaidav.is would know!

I'm so proud of you 🥹