For the problematic paragraphs, a yellow border seems enough to capture the user attention and will provide room to highlight individual elements (e.g., marking in red the specific link or reference that prevents the content from being published).

I have the following implementation.

@Pginer-WMF already has some comments when I showed this to him

• If we cannot achieve "Spanish Wikipedia2 may be better to say "Wikipedia in <language>" instead.
• Distinguish the filter name a bit.
• Avoid having two "more" links next to each other. We can integrate the "view more" into the text by turning the "the restrictions from Spanish Wikipedia" part into a link instead.

In T123912#1986009, @santhosh wrote:

@Pginer-WMF already has some comments when I showed this to him

• If we cannot achieve "Spanish Wikipedia2 may be better to say "Wikipedia in <language>" instead.

This is not any different from i18n point of view, still has the problems of inflection. We could resort to workarounds such as "... target wiki (Spanish Wikipedia) ..." if we wait T121936 to be resolved.

• Avoid having two "more" links next to each other. We can integrate the "view more" into the text by turning the "the restrictions from Spanish Wikipedia" part into a link instead.

Did I understand correctly that "View details" shows the default/customised warning message which is hidden by default and "Learn more" goes to some documentation page (which we haven't yet decided which one it it will be)?

It seems that the detailed messages are often verbose and out of context. So it makes sense to surface them only when more details are needed. I captured some ideas int he mockup below:

• Adjusted the language to avoid using the term "section". "Section" is a term we use to refer to either paragraphs, titles, images or any other block of content; but it can become confusing for users that interpret it as a "document section".
• The general link for more info on abuse filters is provided as part of the default message to better separate the general info from the specific one and avoid having too many "more" actions together.
• The name of the filter ("spambot detection filter" in the example) is provided in the title of the card. As users get used to the same kind of errors that will make them easier to distinguish.
• The "View details" when expanded should become "hide details" (not shown in the mockup), allowing to collapse the info again.
• Use "Wikipedia in language" instead of specific project name. Although the later may be possible once T121936 is completed.

Change 267012 had a related patch set uploaded (by Santhosh):
Linter card: Validate the translation on save

https://gerrit.wikimedia.org/r/267012

Niklas noted the following issues at the above version of patch

1. AF card does not go away if I focus the title
2. AF status is not updated unless I re-focus the section or make a change in the section. I would expect the status to change immediately on save.
3. There is no mention that there can be false positives. This might be important if there will be many of them, but maybe not necessary right now.

I am planning to introduce a hook for validation error after the storage rearchitecture done to address the #2. The issue #1 should go away with the title validation patch(https://gerrit.wikimedia.org/r/269379)

Change 267012 merged by jenkins-bot:
Linter card: Validate the translation on save

https://gerrit.wikimedia.org/r/267012

This patch has been deployed to production via the train, fixing the tag.

Change 273854 had a related patch set uploaded (by Santhosh):
Introduce validation error and success events for sections

https://gerrit.wikimedia.org/r/273854

Change 273854 merged by jenkins-bot:
Introduce validation error and success events for sections

https://gerrit.wikimedia.org/r/273854