-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
No JS fallback for kiwix-serve welcome page #615
Comments
@kelson42 - I'd be happy to work on this if there's need and no one else is tackling it. I've been considering updating kiwix-serve to do something like this regardless. |
@thavelick Yes, you are welcome to work on this ticket. |
We don't have this static list now (except raw xml catalog opds feed) Somehow related to #716, if we don't have js support, we probably want to have this list to point to the "nojs viewer" (raw content) of the zim. |
@thavelick Any news? |
I guess, @thavelick has abandonned the idea to propose an alternative here. We should really define what we want to build exactly. |
I now have something in mind 🙂 The current frontpage is a js page which does specific request to opds catalog, parse the xml result and render the what is parsed dynamically. We may loose some features (as the list of categories) but it should mostly works.
|
@mgautierfr If I read that sentence literally, I think that hardly there is anyone who can do it at all 😉 |
I'm not sure where everywhere there is javascript. But could we maybe first implement #750 in C++ (instead of the js we have currently) first? This would be better from a UX as well. |
Following mgautierfr's words above, I was able to get the same design of tiles without JS (injecting details using mustache in html file): Haven't looked into how language/category filtering concretely for this. But maybe a Current draft: #897 |
Bravo @juuz0 ! |
Yay, finally! 🎊 |
The new kiwix-serve UI is more practical but it's now impossible to use kiwix-serve without JS enabled.
There are many ways to solve this but if we consider no-js to be an edge case, we could, at least have a
<noscript />
tag pointing to a separate endpoint with a static list of contents.The text was updated successfully, but these errors were encountered: