Let's do something more about MacroExecutionErrors

See http://localhost:3000/en-US/docs/Web/HTML/Element/input/search#attr-spellcheck What you see is this:

When you’re in previewing mode (localhost:3000), it’s just a little bit too “discrete”. It should probably “stand out” more to grab a human’s attention to take care of it. Yes, we have the “Show flaws” UI but it’s still potentially not enough.

When in production mode (localhost:5000), it, today, actually looks exactly the same. I think there it should say something “less screamy” but more proactive and helpful like:

<p class="macro-error">
Sorry. An error occurred right here rendering this text inclusion. <br>
To learn more or to help out go to <a href="/en-US/docs/MDN/Getting_Started">learn about how to contribute</a>.
</p>

(PS. we could leverage NODE_ENV==='development' here and load some extra CSS that makes that more red and standing out)

Some help from @schalkneethling and @malqinneh would be appreciated here. We can break this apart between some necessary kumascript rendering stuff and some design work. Plus a shared chat about the correct and appropriate wording/prose.

[teoli2003]

I think we are close to 0 now, so we can easily investigate when new ones appear.

Periodically checking the flaw dashboard and cleaning these is enough. In other terms, I think there are many things more important 😃

/me loves the flaw dashboard, although I don’t have enough time to look at it more often.

I would support to close thiis issue.

[ghost]

Beyond the rest of the management I believe that in CSS it needs to start from the .error class and eventually extend in the future. In the end it should be a simple message always without further functionality.

<div class="error">
 <p class="message">...</p>
</div>

Like the interface’s Instance properties in JS. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error

So this component can be used easily in any catch scope.