Similar like the folks @nodejs have done (https://github.com/nodejs/help), I think we could benefit if all the help related issues on how to use nuxt (or one of its components) would be moved to a separate repo. Maybe even under @nuxt-community so more people can help, clean and resolve issues. But keep this tracker for bugs and features only.
Although the nuxt-trinity :angel: tries to keep the tracker as clean as possible, I still find it quite confusing by time. If you look at the current first page there are only 4 bug/feature issues, the other 21 are all general help related.
Take the memory leak issue currently in rc11 as an example, there are two duplicate open issues about that (1695 and 1728), but they only appear on page 3. I was surprised when yesterday 1984 appeared in which it was mentioned that the bug was (probably) solved already, while that is a great thing unfortunately nothing about that seems to be mentioned in the open issues 1695 or 1728. Probably that's partially caused because its just difficult now to keep track of all the bug issues?
Splitting the help wanted issues into a separate repo should keep this issue tracker much cleaner so its easier:
Probably we would need to add an ISSUE_TEMPLATE that explains this.