Recommend checking the logs for errors #33055

[Tratcher]

Fixes #33055

The error page says to enable development mode if you want to see the error, but it does not say what to do in production. In both environments we should recommend checking the server logs before enabling development mode.

Draft until:

• We confirm we like the text (@danroth27?)
• We get an aka link for the docs (@danroth27?)
• I copy it to the other templates

[danroth27]

Production error pages are often viewed by users of the site, not the site admin. Normal users won't know about Development environments or server logs. Isn't it more typical to have text that says something has gone wrong with the site and that they need to contact the site admin for assistance?

[Tratcher]

We could certainly lead with "contact your site administrator", but I still think we need some comments targeted at the admin "if you are the site administrator...", those are the ones that see the page and contact us for help.

[danroth27]

I don't think the site admin is really the audience for this production error page. The main audience is the end user. Exposing site admin concerns to end users doesn't seem like a good user experience for a website. I think we should remove the existing Development mode content and replace it with something like "Please contact the site administrator for assistance." Leave the request ID, so that the user can share that with the admin.

[Tratcher]

See this example issue: AzureAD/microsoft-identity-web#1213
(There's a secondary issue there where enabling Development didn't help).

We get reports like this from developers that break their site on deployment and don't know how to investigate it. They tell us they want more information on this page, not less. Compare to the ANCM error page that gives diagnostic suggestions:
https://weblog.west-wind.com/posts/2020/Jan/14/ASPNET-Core-IIS-InProcess-Hosting-Issues-in-NET-Core-31