T193584 should have been completed before taking on this work.
We will do the page issues work in a series of steps. The first step would be to adopt the new visual styles for all page issues. These styles will not distinguish issues based on type or severity of the issue. They will also only use the long-form version of the issue on issue text (using hide when compact will be implemented in a separate step). This task will reflect the default state for page issues.
== User story
As a reader, I want the ability to know details about the issues the page I’m reading has so that I can take them into consideration while reading
== Acceptance criteria
Page issues will display the following:
* Issue description
** Issue description will be limited by TBD
* Link navigating to issue modal
* Visual changes as defined below
=== Design Criteria
Generic page issue treatment (rationale for using the lower severity icon for all issue levels: in terms of keeping users trust, it seems like it'd be worse to raise too high an alarm for a low-level issue, than too raise too low an alarm for a high-level issue)
=== Developer notes
* Once T193584 is done, this should simply be a case of adding the new CSS. Implementor should be wary of unused CSS and CSS bloat when working on this (but we may need to accept it as part of this change and to support the A/B test)