As part of the publishing support (T188732), in addition to confirming the success of publishing (T188733) we need to communicate also the issues.
Issues are communicated at two levels of severity:
- **Warnings.** Issues that do not prevent to publish the article, but they may affect its quality (e.g., edit filters tagging short articles) or have unexpected side-effects (e.g., overwriting an existing article).
- **Errors.** Issues that prevent the user from publishing the article. There are two kinds of errors, **technical errors** where the software has some unexpected behaviour, and **content errors** where the piece of content causing the issue can be identified.
Issues can be communicated at different steps of the translation process:
- **Initially.** When the article is loaded to start a translation.
- **While translating.** As the user edits the translation. In particular, after completing one paragraph and moving to the next.
- **After publishing is attempted.** After the user clicks the publish button.
# After publishing attempt
After clicking on the publish button, a message box provides a summary of the issues found at the top of the document (more details will be provided by specific issue cards).
(More design details to be added...)