chore(alert): remaining alert content

Image updates

Author: andrew-ronaldson

packages/documentation-site/patternfly-docs/content/design-guidelines/components/alert/alert.md

@@ -4,14 +4,19 @@ section: components
 related: ['Alert', 'Alert group']
 ---
 
+import '../components.css';
+
 ## Elements
 
 ### Alerts
+
 Alert elements vary depending on the variation of alert. Toast alerts are always dismissible, but bordered inline alerts can be both dismissable and non-dismissible. All other elements are consistent between toast and bordered inline alerts. Plain inline alerts are never dismissable, and consist of only a status area and alert title.
- 
-<img src="./img/alert-types.png" alt="Alert types" width="868" />
 
-1. **Status area**: The status area indicates the severity of the alert with a specific icon and color. 
+<div class="ws-docs-content-img">
+![Alert types](./img/alert-types.svg)
+</div>
+
+1. **Status area**: The status area indicates the severity of the alert with a specific icon and color.
 
 2. **Alert title**: The alert title concisely communicates the alert’s main message. Its text color is coded to match the alert type.
 
@@ -27,18 +32,22 @@ Alert elements vary depending on the variation of alert. Toast alerts are always
 
 An alert group stacks and positions 2 or more alerts in a live region, either in a layer over the main content of a page or inline with the page content. Alert groups should always rank alerts by age, stacking new alerts on top of old ones as they surface.
 
-<img src="./img/alert-group-elements.png" alt="An example of an alert group stacked on a page. Each alert is labeled according to its place in the stack hierarchy: Newest on top, second newest in the middle, and oldest on the bottom." />
+<div class="ws-docs-content-img">
+![An example of an alert group stacked on a page. Each alert is labeled according to its place in the stack hierarchy: Newest on top, second newest in the middle, and oldest on the bottom.](./img/alert-group-elements.svg)
+</div>
 
 1. **Newest notification:** Always appears at the top of the alert group.
 2. **Second newest notification:** Moves down when a newer notification surfaces.
 3. **Oldest notification:** Continues to move down the stack as newer notifications surface, until a user closes it.
 4. **Overflow footer (optional):** Use this when you do not want to display more than a specified number of alerts at the same time on the user's screen. See [Managing overflow](#managing-overflow) for more information about overflow footer interactions.
 
-
 ### Communicating severity
+
 The status icon, background, and alert title are coded to communicate the severity of an alert.
 
-<img src="./img/alert-status.png" alt="alert styles" width="700" />
+<div class="ws-docs-content-img">
+![Alert status](./img/alert-status.svg)
+</div>
 
 |Type   |Icon   |Usage      |
 |---------|--------|--------------|
@@ -51,12 +60,13 @@ The status icon, background, and alert title are coded to communicate the severi
 For more information about what colors to use for status and severity, visit the [Colors page](/design-foundations/colors/#status-and-state-colors).
 
 ## Usage
-Use an alert component when you are trying to give the user essential information in a prominent way. More specific use cases differ based on component variation. 
+
+Use an alert component when you are trying to give the user essential information in a prominent way. More specific use cases differ based on component variation.
 
 ### Customizing alerts
- 
+
 If your use case falls outside of PatternFly's standard alert variations, use [icons](/design-foundations/icons) and [colors](/design-foundations/colors) to create custom alerts that meet your needs.
- 
+
 View custom alerts in action in our [custom alert examples](/components/alert#custom-icons).
 
 ### Managing overflow
@@ -65,31 +75,40 @@ If you don't want multiple alerts to stack and fill the screen until the user di
 
 The overflow link should be configured to navigate to a place where the user can view and manage a complete list of incoming alerts. If a [notification drawer](/components/notification-drawer) is being used, it should open the drawer. You may customize the text accordingly to reflect the result of clicking the link. However, we recommend displaying the number of new/unread notifications present to give the user feedback about how many additional notifications are remaining to view as in the example below.
 
-<img src="./img/alert-group-with-overflow.png" alt="An example of an alert group with overflow footer" width="662" />
+<div class="ws-docs-content-img">
+![An example of an alert group with overflow footer](./img/alert-group-with-overflow.svg)
+</div>
 
 See our [toast alert guidelines](#using-toast-alerts) for more information about using toast alerts.
 
 ## Placement
+
 Toast alerts should be placed in an alert group in the upper-right corner of a page. Use 8px of padding between each alert in an alert group. Alert group alignment on a page will depend on your use case.
 
 ### Toast alerts
+
 Toast alerts communicate information about an update, confirmation, or other activity. A toast alert overlays content in the upper-right corner of the page and disappears when it times out or when the user dismisses it.
- 
-![toast notification placement](./img/toast-notification.png)
- 
+
+<div class="ws-docs-content-img">
+![Toast notification placement](./img/toast-notification.svg)
+</div>
 
 #### Using toast alerts
+
 Use toast alerts to communicate an update, confirmation, or other activity to the user without blocking their workflow. For example, you can use a toast alert to inform the user that their message was sent. You can include links in a toast alert for a user to take action on the event that surfaced the alert, but the links should only be a shortcut for the user. A toast alert should never be used as the only means for taking actions on an alert event.
- 
+
 Toast alerts stack in the upper-right corner of a page. To properly position and stack a set of alerts, use an [alert group](#alert-groups) component. When alerts stack, the most recent alert appears at the top, and others move down as more alerts come in. When alerts are deleted, the remaining alerts move up.
- 
-![alert group](./img/toast-notification-multiple.png)
- 
+
+<div class="ws-docs-content-img">
+![alert group](./img/toast-notification-multiple.svg)
+</div>
+
 Toast alerts should always have a close button so that the user can dismiss them. If you include an automatic timeout for your toast alert, 8 seconds is recommended. Toast alerts should not disappear while the user is hovering over them.
- 
+
 <img src="./img/Toast-alerts-desktop.png" alt="toast alerts in a page" />
- 
+
 Toast alerts are commonly used in the following situations:
+
 - Confirming that a message sent
 - Confirming that an update was made
 - Informing the user that their action was completed successfully
@@ -103,118 +122,133 @@ Toast alerts are commonly used in the following situations:
 
 <img src="./img/alert-group-mobile.png" alt="An example of a centered toast alert group over a mobile view." width="375" />
 
-<img src="./img/alert-group-mobile.png" alt="An example of a centered toast alert group over a mobile view." width="375" />
-
 See our [toast alert guidelines](#using-toast-alerts) for more information about using toast alerts.
 
-
 ### Bordered inline alerts
+
 Bordered inline alerts communicate information about a specific user action on a page. An inline alert appears within the content area and disappears when the user closes it or navigates away from the page.
 
 ![inline notification placement](./img/inline-notification.png)
 
 #### Using bordered inline alerts
+
 Use bordered inline alerts to return feedback as the result of a user action within a page without blocking the user’s workflow. Common uses for bordered inline alerts include form validation and warning messages.
- 
-* **If an alert message applies globally to the content on a page,** place the alert in the page header area just below the title.
- 
+
+- **If an alert message applies globally to the content on a page,** place the alert in the page header area just below the title.
+
   <img src="./img/Inline-alert-page-level.png" alt="global inline alert in a page" />
- 
-* **If the alert applies only to specific content,** place it inline with the page content to call attention to the error.
- 
-  <img src="./img/Inline-alert-specific-context.png" alt="inline alert inline with content" />
 
-* **If the alert is being used to indicate errors,** use an error validation summary at the top of the page to indicate what errors are present. The summary should be a quick, general overview. Show an error alert next to the field that is causing the error. The error message should be concise and actionable. It should tell the user what happened and the next steps needed to fix it. 
+- **If the alert applies only to specific content,** place it inline with the page content to call attention to the error.
+
+  <img src="./img/Inline-alert-specific-context.png" alt="inline alert inline with content" />
 
-  <img src="./img/inline-alert-page-level-with-link-one.png" alt="inline alert inline with link demo 1" /> 
+- **If the alert is being used to indicate errors,** use an error validation summary at the top of the page to indicate what errors are present. The summary should be a quick, general overview. Show an error alert next to the field that is causing the error. The error message should be concise and actionable. It should tell the user what happened and the next steps needed to fix it.
 
-  <img src="./img/inline-alert-page-level-with-link-two.png" alt="inline alert inline with link demo 2" />
+<div class="ws-docs-content-img">
+![inline alert inline with link demo](./img/inline-alert-page-level-with-link-one.svg)
+</div>
 
-* **If multiple errors are present in the same location,** order them from most to least severe. 
+- **If multiple errors are present in the same location,** order them from most to least severe.
 
   <img src="./img/Multiplealert.png" alt="multiple alerts on a page" />
 
-* **If the alert is being used to indicate errors on a modal,** use an error validation summary at the top of the modal below the title to indicate what errors are present. Show an error alert next to the field that is causing the error. The error message should be concise and actionable. It should tell the user what happened and the next steps needed to fix it. 
+- **If the alert is being used to indicate errors on a modal,** use an error validation summary at the top of the modal below the title to indicate what errors are present. Show an error alert next to the field that is causing the error. The error message should be concise and actionable. It should tell the user what happened and the next steps needed to fix it.
+
+<div class="ws-docs-content-img">
+![multiple alerts on a page demo 2](./img/inline-alert-modal-with-link-two.svg)
+</div>
 
   <img src="./img/inline-alert-modal-with-link-two.png" alt="multiple alerts on a page demo 2" />
 
-* **If the alert is being used to indicate errors on a modal with an existing alert,** display the new alert above the existing alert.
+- **If the alert is being used to indicate errors on a modal with an existing alert,** display the new alert above the existing alert.
 
-  <img src="./img/inline-alert-modal-with-existing-alert.png" alt="multiple alerts on a modal with existing alert" />
+<div class="ws-docs-content-img">
+![multiple alerts on a modal with existing alert](./img/inline-alert-modal-with-existing-alert.svg)
+</div>
 
 **The user can dismiss an information alert by using the close button.** Error-related alerts (warning and critical severity) should disappear only when the underlying issue that caused the alert is resolved. However, if the issue cannot be resolved on the current page, use a [modal](/components/modal) instead of an inline alert to provide user the options to proceed.
- 
-In addition to static message content and links, **you have the option of including interactive elements** in the body of an inline alert to ask the user for further input or feedback.
 
- 
-<img src="./img/option-alert.png" alt="alert with radio button options" width="439px" />
+In addition to static message content and links, **you have the option of including interactive elements** in the body of an inline alert to ask the user for further input or feedback.
 
+<div class="ws-docs-content-img">
+![Alert with radio button options](./img/option-alert.svg)
+</div>
 
 Bordered inline alerts are commonly used in the following situations:
+
 - Informing the user that the information they entered into a form field isn’t valid
 - Informing the user of something that needs their attention
 - Informing the user that they need to set something up
 - Informing the user that a feature is temporarily unavailable
 
 ### Plain inline alerts
+
 Plain inline alerts communicate information about a temporarily persistent error or other activity. A plain inline alert is less visually intrusive than a bordered inline alert, and is designed to be placed in content-heavy areas, such as within a form, wizard, or drawer. This alert type persists until the error or action is resolved.
- 
-![plain inline notification placement](./img/plain-inline-notification.png)
+
+<div class="ws-docs-content-img">
+![plain inline notification placement](./img/plain-inline-notification.svg)
+</div>
 
 #### Using plain inline alerts
- 
+
 Use plain inline alerts to communicate non-imperative messages to the user without adding visual clutter. This alert type is particularly helpful within other components, such as wizards, drawers, modals, side panels, and popovers, which may already contain a lot of information.
 
 Plain inline alerts are non-dismissible, and it is not recommended to use them with actions or links.
 
 **Using plain inline alerts on tabbed pages:**
 
 On a tabbed page that has a gray background, inline alerts do not offer enough contrast. Using them in this context requires additional formatting.
+
 - If the alert is relevant to the entire page and all the tabs within the page, it should be placed on the header:
- 
-  ![alert group](./img/inline-header-alert.png)
- 
+
+<div class="ws-docs-content-img">
+![Alert in page header section](./img/inline-header-alert.svg)
+</div>
+
 - If the alert is not relevant to the entire page, the white header area should be extended below the tab and separated from the tabs by a gray line. Place the plain inline alert in the resulting “banner”:
- 
-  ![alert group](./img/below-tab-alert.png)
- 
+
+<div class="ws-docs-content-img">
+![Alert below tab content](./img/below-tab-alert.svg)
+</div>
+
 Plain inline alerts are commonly used in the following situations:
+
 - Informing the user of something that needs their attention
 - Informing the user that a temporary error has occurred
 - Informing the user that a feature is temporarily unresponsive
 
 ## Content considerations
- 
+
 - In inline alerts and toast alerts, avoid using “success” and “successfully.” They’re extraneous.
- 
+
 <div class="ws-content-table">
- 
+
 | **Do** | **Don’t** |
 |:------:|:---------:|
 | Account created| Your account was successfully created.|
- 
+
 </div>
- 
+
 - Be concise. In one-line toast alerts, use fragments instead of sentences if possible.
- 
+
 <div class="ws-content-table">
- 
+
 | **Do** | **Don’t** |
 |:------:|:---------:|
 | Message sent| Your message has been sent.|
- 
+
 </div>
 
 - In toast alerts containing links, describe how the user can navigate through the UI to perform the action. Learn more about how descriptive text supports accessibility in the next section.
- 
+
 <div class="ws-content-table">
- 
+
 | **Do** | **Don’t** |
 |:------:|:---------:|
 | From the **Settings** tab, click **View logs.**| **View logs**|
- 
+
 </div>
- 
+
 ## Accessibility
 
 For information regarding accessibility, visit the [alert accessibility](/components/alert/accessibility) tab.