feat: redesign 404 page with error image and fix GitHub Pages routing#810
feat: redesign 404 page with error image and fix GitHub Pages routing#810
Conversation
…ting Add error illustration and visual improvements to all three language versions of the 404 page. Replace the Hugo alias-based 404.html (which landed under /en/404.html due to defaultContentLanguageInSubdir) with a static/404.html that reliably serves from the root on GitHub Pages. Fixes #717 Fixes #136
|
Hi there! 👋 Thank you for your contribution to the FIP Guide! 🚀 Checklist before merging:
|
✅ Deploy Preview for fipguide ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
The contrast of the image in dark mode is pretty bad.
There was a problem hiding this comment.
Feel free to change the image :)
There was a problem hiding this comment.
What do you think of the new one (source https://www.pexels.com/de-de/foto/30503335/)
| <div class="o-error__divider"> | ||
| {{ partial "intersector" }} | ||
| </div> |
There was a problem hiding this comment.
I’d not show it overall, because it doesn’t divide two paragraphs.
| @@ -0,0 +1,23 @@ | |||
| {{ define "main" }} | |||
| <article class="o-error" data-pagefind-ignore="all"> | |||
There was a problem hiding this comment.
I’d prefer this one:
<article class="o-single o-single--error" data-pagefind-ignore="all">
There was a problem hiding this comment.
Not sure about it, the error case is pretty specific and isolated, we won't use it in another file. So I'd keep it in a separate SCSS file and not mix it in the content SCSS file. Another idea is to rename it to o-404 or something like it.
There was a problem hiding this comment.
I didn’t talked about scss at all. The syntax and the file-system are two different things in my opinion. In BEM this is a special case for o-single, so we should treat it like that :)
There was a problem hiding this comment.
I always prefer a clear logic to find out in which SCSS file a CSS rule is stored and the prefix is the easiest one to remember. But we don't do that consistently, so yeah, we can also call it o-single--error.
However, we should then also update the other elements as well, for example o-error__body--error and so on.
There was a problem hiding this comment.
if we do so, we should update the other elements as well, yes 👍🏼 I agree with you to have a clear logic – let’s discuss the scss file structure in another issue :) #879
There was a problem hiding this comment.
We can get rid of the file now, right?
| - **Accédez à la page d’accueil :** Retournez à la page d’accueil et naviguez à partir de là. | ||
| - **Utilisez la navigation :** Essayez de naviguer via le menu ou d’utiliser la fonction de recherche. | ||
| - **Contactez-nous :** Si vous avez besoin d’aide, n’hésitez pas à nous contacter : [nextstop@fipguide.org](mailto:nextstop@fipguide.org) | ||
| - **Vérifiez l'URL :** Assurez-vous qu'il n'y a pas de faute de frappe dans l'adresse. |
There was a problem hiding this comment.
| - **Vérifiez l'URL :** Assurez-vous qu'il n'y a pas de faute de frappe dans l'adresse. | |
| - **Vérifiez l’URL :** Assurez-vous qu'il n'y a pas de faute de frappe dans l'adresse. |
You probably used a Anthropic model. They have the bug that they replace ’ with '. It's a bit annoying. Can you change it back for all occurrences in the file?
| @@ -0,0 +1,23 @@ | |||
| {{ define "main" }} | |||
| <article class="o-error" data-pagefind-ignore="all"> | |||
There was a problem hiding this comment.
Not sure about it, the error case is pretty specific and isolated, we won't use it in another file. So I'd keep it in a separate SCSS file and not mix it in the content SCSS file. Another idea is to rename it to o-404 or something like it.
Summary
error.webp) and improved layout usingfloat-imageandintersectorshortcodes across all three languages (en, de, fr)404.html(which incorrectly landed under/en/404.htmldue todefaultContentLanguageInSubdir: true) with astatic/404.htmlthat reliably serves from the site rootcenterposition support forfloat-imagein SCSSFixes #717
Fixes #136