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

Improve look&feel of the Kiwix Server 404 page #710

Open
kelson42 opened this issue Oct 4, 2024 · 19 comments
Open

Improve look&feel of the Kiwix Server 404 page #710

kelson42 opened this issue Oct 4, 2024 · 19 comments

Comments

@kelson42
Copy link
Contributor

kelson42 commented Oct 4, 2024

The Kiwix Server 404 page is displayed when an HTML page is requested but does not exists in the ZIM file. A 404 error is an HTTP status codethat means the page you were trying to reach on a website couldn't be found on their server.

Today it looks like this:
Image

This page should obviously localisable.

Here is the link: https://dev.library.kiwix.org/viewer#opentextbooks_en_all_2024-09/openstax.org/subject_does_not_exist

This scenario should happen rarely as ZIM are conceived to remove - as much as possible - the kind of dead links leading to such a page. But this error will always happen time to time.

Today the page is informative but really not fancy. We would like to improve it with a nice design and a Kiwix specific visual:

  • Like the the dead Kiwix visual
  • We have also a dedicated customised 404 logo

On my opinion we might not put more in emphasis the "404" which is a pure HTTP error and in some cases the readers are not HTTP related, so this might be abusive.

Here a few very nice 404 pages
l

@siemsie
Copy link

siemsie commented Oct 8, 2024

Hi @kelson42 . Can you just clarify your last phrase, you would like a 404 reference, or not? Thanks.

@kelson42
Copy link
Contributor Author

kelson42 commented Oct 8, 2024

Hi @kelson42 . Can you just clarify your last phrase, you would like a 404 reference, or not? Thanks.

I suspect that it would be better to not make an explicit reference to the code "404", neither in the text, nor in the visual.

@siemsie
Copy link

siemsie commented Oct 14, 2024

Hi. Here are some first ideas.

Image
Image

@kelson42
Copy link
Contributor Author

@siemsie Thank you! We will gather feedbacks so we can make an educated chose/response
@juuz0 @veloman-yunkan @rgaudin @Popolechien @sgourdas @benoit74 @ShaopengLin Your feedback is welcome about what is good and what could/should be improved.

@kelson42 kelson42 modified the milestones: 3.9.0, 3.8.0 Oct 14, 2024
@Popolechien
Copy link
Member

Popolechien commented Oct 14, 2024

V1 looks nice but why not go with the 404 we already have on our website?
Image
There is a bit of text on top

Sorry – we can't find what you are looking for!
We are sorry, the page you requested could not be found.
Please go back to the [homepage](https://kiwix.org/en)

@benoit74
Copy link

I agree that we must not mention 404, this means nothing to most users.

My preference is for version 2.

I would prefer to revisit a bit wording:

  • The request URL => The requested path or The requested ZIM item (with a preference for "path" for simplificity)
  • not found on this server => not found in this ZIM

Regarding the "Make a full text search for ..." paragraph, I feel like it provides way more frustration than value. It is very technical ("full-text search" is a complex term) and very very rarely works from my experience. I would at least replace it with a constant text with something like You might want to search for this content instead of accessing it via the link you just clicked, maybe this is just a broken link issue and this content is present at another path in the ZIM. And not automatically suggest search terms which are mostly always bad in my experience.

@rgaudin
Copy link
Member

rgaudin commented Oct 15, 2024

  • I find the v1 too different from the usual visual of kiwix-serve
  • I find both v2 and v3 to not convey the proper meaning.
  • I find the 404 to be too tied to understanding what 404 stands for which is probably not the case for a huge share of our user base.

I agree with @benoit74 on the wording

@siemsie
Copy link

siemsie commented Oct 15, 2024

Image
These are images we already have (I made v5 with the ?). Could there be something there that works better?

Either way, need to have consensus on the overall message to find a suitable image. Are we lost? Is it broken?

@sgourdas
Copy link
Collaborator

While I feel that the 404 is not essential for the every day user to see, I observe that most webpages still choose to display it in some minor way. It seems like everyone understands the general meaning of it, after getting used to seeing it everywhere.

As far for the samples, I am in favor of being consistent with the main website as @Popolechien mentioned, but we should keep the focus on the important details of what happened. In that sense the 404 could be put beside a bigger image of v3, v4/v5 or v6, so they can be used together.

I also think that it is good to provide some getaway resources like links to the home page and more direct and relevant hints like @benoit74 mentioned.

@kelson42
Copy link
Contributor Author

kelson42 commented Jan 2, 2025

We are working now actively to complete and release 3.8.0 and therefore come back on this. Thank you all for your valuable feedbacks.

@siemsie Can you please propose a white page like v2/v3 but with the v5 logo AND the wording (for both lines) proposed by @benoit74 ?

@rgaudin @benoit74 I think we could implement v3 for 5xx like errors. What do you think?
@rgaudin @benoit74 Should we already request/implement a darkmode version? Or is that too early?

@kelson42 kelson42 self-assigned this Jan 2, 2025
@rgaudin
Copy link
Member

rgaudin commented Jan 2, 2025

@rgaudin @benoit74 I think we could implement v3 for 5xx like errors. What do you think?

Absolutely. Just checked and neither 404 nor 500 responses uses templates. Both deserve a nice handling.

@rgaudin @benoit74 Should we already request/implement a darkmode version? Or is that too early?

Too early IMO given neither the ZIM content nor the homepage support it.

@benoit74
Copy link

benoit74 commented Jan 6, 2025

@rgaudin @benoit74 I think we could implement v3 for 5xx like errors. What do you think?

No opinion

@rgaudin @benoit74 Should we already request/implement a darkmode version? Or is that too early?

No opinion

@siemsie
Copy link

siemsie commented Jan 8, 2025

Hi all. I hope I understood the request of mixing and matching the previous versions. Here is a v7 and v8. v8 is a rewrite to make shorter and more direct phrases... not sure what I wrote is correct, but can fix that with a v9 if it is the direction we take.
Image
Image

Re dark versions, the Kiwix can't be in white, but a white area can be redefined around the content... let me know if/when it becomes a need.

@rgaudin
Copy link
Member

rgaudin commented Jan 9, 2025

Thank you ; I find v8 more readable with the white background and extended text. Feels like effort is given around helping sort out the issue.

Would if be possible to use a single sentence for “The requested path was not found:” and then have it followed by the actual path? I find the cut version weird and it might be difficult to translate.

Also, I think it's important that the path is displayed on a monospace font. Goal of this being to identify typo and such. I don't think with it on its own line the quotes provide any value (can even be misleading).

@benoit74
Copy link

benoit74 commented Jan 9, 2025

I second all Renaud points.

@siemsie
Copy link

siemsie commented Jan 9, 2025

Ok here is a v9 taking into account your comments @rgaudin. Thanks for the feedback.
Question: Does it make sense to have a "page not found" following by a "requested path not found"? The top part is a pretty standard phrase which we all recognise (but is effectively a 404) - does it apply?
Thanks.

Image

@rgaudin
Copy link
Member

rgaudin commented Jan 9, 2025

LGTM ; I dont mind the repetition. I think the title is more general information than a technical reason (where some subtleties might lie)

@benoit74
Copy link

benoit74 commented Jan 9, 2025

LGTM as well, I don't mind the repetition either.

@siemsie
Copy link

siemsie commented Jan 9, 2025

Let me know what you need then and when you need it by, and if there are any further changes. Image, font, sizes and colours? Or just the vector file directly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants