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

Docs: create nice 404 pages #3444

Merged
merged 2 commits into from
Aug 2, 2022
Merged

Docs: create nice 404 pages #3444

merged 2 commits into from
Aug 2, 2022

Conversation

humitos
Copy link
Contributor

@humitos humitos commented Jul 13, 2022

Summary of changes

Currently, when a user arrives at a 404 page, Read the Docs shows the default Maze Found page without context about the setuptools project itself.

This extension, sphinx-notfound-page, creates a 404.html page with the same style as the rest of the documentation pages that Read the Docs will serve instead of the default Maze Found one.

This PR suggests installing this extension so readers of this documentation have nicer UX when dealing with not found pages. I st up a Read the Docs project as example to show the behavior, take a look at this not found page https://humitos-setuptools.readthedocs.io/en/docs-notfound-page/notfound

Let me know if there is any modification you want me to do or any feedback you may have.

Example

Screenshot_2022-07-13_12-50-06

Pull Request Checklist

humitos and others added 2 commits July 13, 2022 12:46
Currently, when a user arrives at a 404 page, Read the Docs shows the default
Maze Found page without context about the setuptools project itself.

This extension, `sphinx-notfound-page`, creates a `404.html` page with the same
style as the rest of the documentation pages that Read the Docs will serve
instead of the default Maze Found one.
@@ -90,6 +90,7 @@ docs =
jaraco.packaging >= 9
rst.linker >= 1.9
jaraco.tidelift >= 1.4
sphinx-notfound-page == 0.8.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a merge to fix the conflict (and decided to leave the version pinned because the extension haven't achieved 1.0 yet).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! It has been pretty stable and we don't have plans for big changes under the radar --but I think it's fine to use the pinned version as a way of self protection just in case 😄

@abravalheri abravalheri merged commit 9b0cf7e into pypa:main Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants