Hi, thanks for the suggestions, let me just comment on a few.
yes, I think it’s unlikely we’ll launch more than dark/light themes, although we might improve these. Basically color themes are easy to get 95% right, but really fussy for the edge cases, so it could well be useful for individualization. Since colors are governed by a limited set of variables, it’s trivial to make a theme. In fact you could easily make a theme builder and let people define their own colors.
If there was a simple CSS implementation of this, which could be activated via hotkey or via the settings panel, I’d listen.
That’s a great idea, although I would be open to further native improvements. Maybe if you explore this let us know if there are any that you think might be useful globally.
Yes, we won’t implement this.
I am open to changing the view settings, although horizontal scroll will always be necessary depending on screen width. If someone can design a better way, happy to consider it. But we don’t have developer resources at the moment.
Yes, we would not do this.
Hmm, maybe we would do this. I dunno, it feels like more complexity to do something that’s easy enough. But maybe for mobiles it would be better, so yeah, if there was a simple and lightweight option I’d consider this.
Nope.
Hmm. Our overall development priority is to deprecate legacy translations and promote segmented translations. So I’d be more open if this was a simple alert: you’re on a legacy translation, and yes, a segmented translation is available.
(For those new to this, just to repeat: the only reason we have multiple translations is that in the past there was no single set of good translations, so we just got what we could. Most of the legacy translations in English are not all that great—although of course there are exceptions. We’ve supported translations from more translators than any other site, but I must confess there comes a time when I am less than enthused about spending years improving translations only to send people back to less accurate versions, sorry. People get into the bad habit of comparing translations to find the one they like. But the reality is that when a new translation is made, the translator is well aware of the old interpretation and changes it deliberately. And unless you know Pali well, you really don’t have a basis for judging the work. I don’t know how many times people have said to me, “I really like the way X translated Y”, but I’m, “You might like it, but that’s not what the Pali says.” And if you do know Pali, then you should be looking at the Pali. Rather than comparing translations, I highly recommend sticking with the segmented translations, checking the Pali with the lookup tool, and when you have questions, ask them here.)
This is a bit complicated, let me comment on that issue.
Yeah, probably not something we’d implement. Better for a browser extension.
Umm, yeah, I’ve given some thought to this over the years, or else “recommended” and the like, but nothing has really tickled my fancy. I’d be open to something if there was a strong and clear proposal. But yeah, unlikely we’d do a “random sutta” button.
Yeah, again unlikely we’d do this.
I’m happy with our current navigation.
I’m using Papaly for this, TBH it could be improved from a technical point of view, but it does the job.