/wbDoc — ELI5

You built a gadget. Somebody buys it. It comes with no manual.

/wbDoc writes the manual. For packages, that's the README. For individual functions, that's the JSDoc comments above them.

Good docs explain how to use the thing and what not to do. Not "this function takes an argument called x" — that's what the code already says.

Run it before shipping a package. Run it again when you add something new. Skip it for code that's about to be refactored — you'd write docs for code that's about to disappear.

---