Describe the bug
The 404 page for docs-tools isn't a complete match for the 404 page on the main BeeWare website - the body content is very similar, but its missing the header and some other styling.
Steps to reproduce
- Go to https://beeware-docs-tools.readthedocs.io/en/latest/does-not-exist
- Compare with https://beeware.org/does-not-exist
Expected behavior
Pages should be substantially the same style
Screenshots
No response
Environment
- Operating System: all
- Python version:
- Software versions:
Logs
Additional context
The complication is linking resources - the CSS and JS needed to display the default toolbar.
As the docs-tools site is multi-lingual, the root of the site is /en/latest; and serves assets as /en/latest/assets/... however the 404 page is trying to load assets from /assets/....
Two possible approaches:
- Find out how to reference the "site root" as part of mkdocs, and use that in asset references in the head block
- Reference the "live" versions of those resource in the head block. This would mean 404 resources are pointing at potentially stale resources; but it's a 404 page, so it's not critical that they're always live.
Describe the bug
The 404 page for docs-tools isn't a complete match for the 404 page on the main BeeWare website - the body content is very similar, but its missing the header and some other styling.
Steps to reproduce
Expected behavior
Pages should be substantially the same style
Screenshots
No response
Environment
Logs
Additional context
The complication is linking resources - the CSS and JS needed to display the default toolbar.
As the docs-tools site is multi-lingual, the root of the site is
/en/latest; and serves assets as/en/latest/assets/...however the 404 page is trying to load assets from/assets/....Two possible approaches: