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

Customize 404 page when deployed #1074

Closed
3 of 6 tasks
jonas-jonas opened this issue Nov 10, 2022 · 2 comments
Closed
3 of 6 tasks

Customize 404 page when deployed #1074

jonas-jonas opened this issue Nov 10, 2022 · 2 comments
Labels
feat New feature or request. stale Feedback from one or more authors is required to proceed.

Comments

@jonas-jonas
Copy link
Contributor

jonas-jonas commented Nov 10, 2022

Preflight checklist

Describe your problem

The current 404 page of the docs is not customized and just shows the generic vercel error page, with a link to their docs.

See here https://www.ory.sh/docs/this-does-not-exist

Describe your ideal solution

Provide a custom 404 page with the Ory docs header and footer, and some helpful text and links back to actual content.

Workarounds or alternatives

n/a

Version

master

Additional Context

https://www.ory.sh/docs/this-does-not-exist

@jonas-jonas jonas-jonas added the feat New feature or request. label Nov 10, 2022
@tomekpapiernik
Copy link
Contributor

facebook/docusaurus#6030

Copy link

github-actions bot commented Apr 3, 2024

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Apr 3, 2024
@github-actions github-actions bot closed this as completed May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request. stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

2 participants