[Feature] Error pages are not styled/themed

[TimidRobot]

Problem

Error pages are not styled/themed

Current 404 page:

Description

The error pages should not disrupt the user experience

• error pages should be a resource lite as possible
  • (this issue mustn't be solved with Legacy (Vue) Vocabulary)
• error pages should be should be styled/themed (without being "heavy").
• Need lightweight self-contained HTML error pages vocabulary#1

Alternatives

Do nothing

Additional context

• Creating a custom 404 page for your GitHub Pages site - GitHub Docs

Implementation

• I would be interested in implementing this feature.

[akshansh-modi]

@TimidRobot I would be interested in implementing this feature. , could you please assign this to me

[TimidRobot]

@TimidRobot I would be interested in implementing this feature. , could you please assign this to me

@akshansh-modi Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and PRs.

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a pull request (PR). Even if multiple people submit PRs for the same issue, multiple ideas and implementations strengthen the final product.

[ankur-kalita]

hey @TimidRobot I want to contribute to this issue , could you assign me this issue

[kritika-76]

hello !
actually i want some help from you to start the project and how to start .
i am the beginner and i am trying to do projects .
but by some queries , i won't make it.
can you please help me as a mentor?

[saikatsardar01]

@TimidRobot How about this page?

404-page-uh-oh-you-re-lost.mp4

[saikatsardar01]

If you like it I can give a pull request

[egbadon-victor]

@TimidRobot @possumbilities I was doing research on the implementation of this.

Could this be implemented upstream in the vocabulary repository. The reason for this thinking is as follows;

• All CC ancilliary sites don't have a uniform error page implementation.
• All sites have the same class of errors that could occur (i.e 4xx, 5xx etc), hence a design system can effectively accomodate these variations.

While a PR can be submitted for this specifically for this issue, I think it would be a great opportunity to standardize the error page structure.

Here is how I would go about it;

1. Implement the error page styles in the vocabulary repository, along with creating a specimen in the context folder, to visaulize the error page, collaborating with project maintainers for feedback.
2. Update the vocabulary version of the chooser repo to reflect the error styles update
3. Implement the error page in the chooser repo, following the approved design system arrived at in step 1.

Please let me me know what you think about this.