Open elycheea opened 5 months ago
Given @davidmenendez’s recent refactor of empty state, I would suggest that we set a call with at least @thefirstartist @davidmenendez to define the acceptance criteria for this issue.
@devadula-nandan Not that I was expecting to see many issues with full-page errors, but happy to share that accessibility review passed with only one non-blocking issue! Assigned to you but don’t think you need to address it right away either since it’s a lower priority cleanup. We have the tiniest bit of redundant code in Storybook. 🙂
Full page errors
Brief description
Display a full-page error when the requested page is unavailable to the user. This is typically caused by issues with the requested URL or access permissions. Errors caused by server connectivity issues are not covered in this guideline.
Details
This pattern is intended to replace the current version of HTTP errors.
Link to design Current version (3 variants — 403, 404, other)
Links to other materials
e.g. sketch files, icons, images, prototypes
Design Maintainer(s)
Tasks
Before starting work on this epic, please review and complete the following.
Working in Carbon for IBM Products package