Please drop the "New feedback experience" idea

[i3v]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Document new Get-Foo cmdlet" instead of "New cmdlet."

Summary

The "New feedback experience" (see #3716) is a HUGE step back from the current GitHub-based approach!
I beg you to cancel these plans!
Also, please do not move existing issues to another repository (this is a very annoying and very bad Microsoft's habit to ignorantly remove existing articles/documentation like this.

Details

Existing github-based issue reporting is great! Almost best-in-class (maybe YouTrack is a bit better, but not much).
Everyone can search through the questions and find some additional useful information (questions/discussions) related to particular articles and even potentially contribute some changes to the articles, after actually finding a solution. It also provides at least a theoretical possibility to find an existing question that would match your own question (which must provide a native deduplication).

The newly proposed "Was this page helpful?" is just crap. Like effectively every other feedback method, it would just produce no effect. So, there would also be no motivation to use it.

The "make it easier for you to submit feedback" is a very incorrect motivation at all. There's nothing "too difficult" with the current approach at all. Personally, I would not mind if those "simple and small" form would exist there, if Microsoft would keep the existing "github" way to report issues.

Proposed Content Type

Concept, Other / Unknown

Proposed Title

No response

Related Articles

#3716

[exchange12rocks]

I must say I agree: I like to improve these docs when I have free time, and by looking at issues other people reported I can quickly see areas where I can help. #3747 for example

Sometimes issues can even have deeper discussions where you can find how to solve your problem/correctly work with a particular tool even before a correction to the docs is published.

I believe opening documentation sources and allowing the community to collaborate is one of the best things the "New" Microsoft has done.