InTheDesert wrote: ↑March 19th, 2024, 11:15 pm
TriciaG wrote: ↑March 19th, 2024, 9:01 am
That would be a lot of programming. I'm not sure it's feasible.
It's actually pretty
clean and small.
I agree that it should be technically possible, with enough effort, to achieve the effect you are after — though to be honest I really can't see why you would want to single out this one tiny element (in many cases only a single line long) out of all the other elements on this page for the special game of hide and seek you're proposing. Why stop at hiding keyterms? What about zip file size, say? What about all those different downloading/accessing modes listed on the page? What about Genre? Why single out keyterms alone for such treatment?
As for "pretty clean and small", everything at w3schools is "pretty clean and small". That's quite appropriate, because the site only intends to deliver rudimentary tutorials. I'm not knocking that site at all. I've learned a lot from there over the years - but one of them is that the solutions they offer are only rudimentary, and often need a lot of modification and extension before they're of any use in a realistic scenario.
If you want to see what anyone implementing the kind of "pretty clean and small" solution would actually be up against, please use the option in your browser that allows you to view the source code of the catalog page for any Librivox audiobook. Scroll to the bottom, and you will see several hundred lines of Javascript. That Javascript is a little more complicated than anything you'll see in a w3schools tutorial. Once you've viewed that code, ask yourself (a) how the w3schools "pretty clean and small" solution that seems so apt as a matter of general principle could fit in with what's already there, and (b) how you can be sure that by implementing the w3schools "pretty clean and small" solution you won't be breaking anything that's already working.
If I come across as a bit of a defensive nark in what I've said here, I should apologise right now. I can only say in my defence that the discussion in this most thought-provoking thread have led me to a completely new appreciation of (a) how few resources librivox.org has to fall back upon when it comes to implementing technical changes, and (b) the actual complexity of what's involved in setting up a development environment to try out even seemingly "pretty clean and small" changes for possible incorporation in the live site, and the rather steep learning curve that anyone wanting to step into these waters is likely to face (unless they happen already to be familiar with the architecture of an application like the librivox catalog's). It IS possible to step into these waters with enough determination and effort, I have found — but it's certainly nothing like as simple and easy as your "it's actually pretty clean and small" appears — at least on the surface — to imply.
I do think it's important, though, with limited resources, to focus on things that actually matter — and I don't think hiding keyterms actually does.