Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Implementation of an error page context. #306

Closed
1 task done
egbadon-victor opened this issue Nov 6, 2024 · 2 comments
Closed
1 task done

[Feature] Implementation of an error page context. #306

egbadon-victor opened this issue Nov 6, 2024 · 2 comments
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on

Comments

@egbadon-victor
Copy link
Contributor

Problem

As it stands, vocabulary does not specify any standard for styling error pages. Inspecting the various existing error pages on the CC Ancillary sites, some have different implementations.

CC Legal DB and Open source

image

CC Search Portal

image

Description

By implementing a standard for CC error pages, it makes it easy to identify error pages that are not properly implemented, as well as serve as a guide for implementation in new projects.

Alternatives

  • Make all error page implementations local to the downstream project (Not recommended)
  • Do nothing

Additional context

This issue is related to;
[Feature] Error pages are not styled/themed #532

Implementation

  • I would be interested in implementing this feature.
@egbadon-victor egbadon-victor added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Nov 6, 2024
@possumbilities
Copy link
Contributor

This is already covered by:

Closing as duplicate.

@possumbilities possumbilities closed this as not planned Won't fix, can't repro, duplicate, stale Nov 7, 2024
@github-project-automation github-project-automation bot moved this from Triage to Done in possumbilities Nov 7, 2024
@possumbilities possumbilities added ⛔️ status: discarded Will not be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 7, 2024
@possumbilities possumbilities self-assigned this Nov 7, 2024
@egbadon-victor
Copy link
Contributor Author

@possumbilities didn't see it all the way up there 😂.

Ill move my suggestions to that issue. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on
Projects
Archived in project
Development

No branches or pull requests

2 participants