Your comment is totally wrong. Any package that's more than a quick hack has inline documentation in a ;;; Commentary: blog, docstrings for all public variable

Your comment is totally wrong. Any package that's more than a quick hack has inline documentation in a ;;; Commentary: blog, docstrings for all public variables and functions, and customisation options for setting variables with an interactive interface w/ documentation and accepted values integrated. Bigger packages come with info files. All sorts of help is accessible by a multitude of entry points, most bound to convenient and consistent shortcuts. Package system requires remote repositories just like any other package system, and Melpa is a third party repository, so that's not surprising at all. The GNU Elpa archive is configured by default. And the list-packages interface has package descriptions, and can show package details by a single keystroke. Selecting and installing/removing multiple packages is possible. If configurability is a burden on you just quit Emacs because that's its biggest point which makes it a very productive tool. And just like a sponge won't clean your tabletop by itself if you don't put soap on it and rub it to the tabletop, Emacs can't do anything for you if you don't learn how to use it and actually use it.