Is there a better way to debug Kirbytag failures?

Usually when something “wrong” happens in a Kirbytag, it’s tricky to figure out what went wrong. In most cases that I’ve experienced, the only indication that something went awry is Kirbytext parsing is abandoned and the raw Markdown text is used instead.

I understand this is the intended “failsafe” behavior, but it seems to mask what the actual problem is (error? exception? etc.).

Are there some suggested techniques to quickly surface information about failures?

You could use the kirbytag() helper.