You can create a new documentation page, a new tutorial contribution, hack Westbam’s westtricks, join github community…
Anyway, it’s impossible to fit into a helppatch all of the “consequences” of a node; once an user told me: “This should be the helppatch of SetSlice and GetSlice”, but just because what I shown was just solving its very problem, not because it was a really general demonstration of those nodes functionalities.
This will be a bit OT, but…
IMMHO, vvvv nature is sometime misleading, because the constant flow of data (I do this, lets see what happens… ah yes I get this; then to get that I add this and that… oh no it’s broken, but what if… LOL broken again… ah, ok. I need that… Yes it is it…) may get you to stick to a specific point of view on the problem, something that may not happen when you have to compile your code before you’re able to see actual results. Don’t get me wrong, it’s just a matter of approach to code. Using only the constant flow could not be the best choice; instead, fore-thinking before starting to spread nodes on the patch could be a better approach.
There’s a page somewhere in the documentation (probably related to a Node, or was it the Parasitic design? Ah…) where IIRC @joreg explains why you should “plan” your patch, and why is not so obvious to patch some logic, much, much better than I’ve done.