Should open source projects keep "how do I" questions out of GitHub issues?

I've never maintained an open source project. So treat this as an outsider's view, and tell me where it's wrong.

From the outside, GitHub issues seem to do three jobs at once: bug reports, feature requests and "how do I install this on Windows?" Maintainers answer the same questions again and again.

After reading what maintainers and the Open Source Guides recommend, this is the split I'd try:

• Confirmed bugs and tracked work stay in issues.

• Settled answers go in the docs.

• How-to questions, ideas and show-and-tell go to a community.

• The best community answers move into the docs.

Does that actually take load off maintainers? Or is it just one more place to check?