Update error pages
What does this MR do and why?
- Align styles with product empty states
- Update illustrations
- Remove old illustration, others will be removed from the library in the future
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Before loading Ruby
| Before | After |
|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
After loading Ruby
| Before | After |
|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
How to set up and validate locally
There are two types of errors:
- before-ruby-starts errors -> http://gdk.test:3000/root/not-existing-project. These pages don't have access to any libraries. So, we need to use custom CSS styles and illustrations here.
- ruby errors -> http://gdk.test:3000/404. These pages have access to our libraries, but these pages should be as lightweight as possible.
You can use these pages to view other errors by replacing the haml code. I think it's the easiest way to test UI
Edited by Julia Miocene