Can we please have a button to flag certain documentation articles?

General Feedback & Requests
, , ,
1

Your documentation is starting to look pretty broken again.

Please give us a flag button at the bottom of each article. Ideally this alerts the author, and also adds the article to an internal list which tracks how many flags have been raised since last article update.
Microsoft’s documentation (after they bought github) should be something that you can aspire to.

Broken links, Broken rendering, Missing content … and that’s not even including the stuff that has fallen out-of-date, or worse - when the author has attempted to keep it up-to-date and now the information is just a muddle of images contradicting text contradicting notes (which are slapped in various places in the article).

I’d really rather use my community time learning and helping people, rather than adding to the noise on here. Many members have tried expressing the same. Please consider the clarity that a simple flag can bring.

Thank you very much and keep up the good work - UEFN is an amazing product.
Hix

2

Broken rendering of code blocks: (Firefox + Chrome)
Broken links from before locale was hard-coded into URL.

3

Broken rendering:

4

Conflicting info.
Incorrect info:

  • the note slapped at the top is a “solution” to the previous article but is only partially correct.
  • The Final 2 steps are completely incorrect. So is layout step 8.

The linked TMNT UI tut works perfectly without the TobjecPtr workarounds this article needs. It also clarifies what broke in the other tut (if you read between the lines).

5

Broken URLs from before locale was hard-coded into the URL’s: