There are two things that I enjoy: a test framework written in my own Domain Specific Language (DSL) that is easily understood by all those on a project and the ability for all participants to easily read, search, and view the tests.

Rules formulated with openVALIDATION are thus at the same time a formal, machine-processable specification, but also a documentation that is easy for people to understand.

Code explains what and how Documentation explains why.

So make sure to write your documentation, but do not explain your spells.

I hope you'll forgive me for defaulting to the documentation: I think it will do a better job of explaining it than me.

What this means is: I better refrain from writing a new book and we rather focus on more and better docs.

I'm afraid there's only so much the docs & tutorials can do about something like this actually. When you first read them, you don't get Svelte well enough (since you're reading a tutorial...) for this to make sense to you. Then you try something, encounter a behaviour, question it, understand better... That's learning.