Following idea for a new usability feature:
In my workflow, I’m using Discourse to spend much time with reading. Most of these posts can become very long, due to the fact, they are about legal questions There are long cases and much longer “solutions” of them.
What I’m really missing is an integrated reader mode. Safari e.g. won’t allow me to enable the browser reader mode (Why?). The default text size is okay for short texts and quickly reading them. But for real focusing on content, there is soo much “wasted” (often empty) space.
In addition to that, maybe - just maybe -, it would be a veryyyyy sexy feature in addition to that, if the user will be able to add highlights on text passages. Maybe some one colour for private notes and one for publicly sharing.
What do you think guys?
I can’t see any use for this feature. We do want to ship an integrated big and small fonts mode.
It’s good for just reading. Many browsers have reading mode and some html trickery to turn it on. Reading modes take up less resource on the browser and they can be in font sizes that is comfortable to individual.
Not the functionality definies a community portal!
Therefore the FOI shouldn’t be ignored beside all the great features Discourse offers. There is a lot of potential for improvements.
You can append
/print in the topic address (or use CTRL + P in desktop) to export a topic to read later too. May help in your use case.
Not really. I just wish, this tiny button would work as expected and shows me the full text of each topic I’m currently reading. Not just randomly selected / pre-loaded ones.
New too. Quite a few times I was reading long topics on meta and by reflex presses the reading mode button, then realized that it didn’t work on this site.
Let’s say, I have five topics that I’m interested in reading. I don’t want to read them one by one or I’ll forget about them, or their order will shift. I don’t want to bookmark them because it is a hassle.
In this very common case, I’ll just load each topic in a separate tab. Clean and tidy. Except that it uses up a lot of resources on mobile. The perfect solution is to press reading mode in each and turn them into text, as after reading I won’t need it to go back. I’ll just close.
Unless Apple provides a DOM event for reader mode, that we can cancel, redirect you to the
/print version of the topic and then trigger again for you, this is impossible.
Isn’t there already certain markup/css stuff that can mark certain elements in a particular page as the context text? If a page is loaded and the browser finds those tags, it will enable reading mode, AFAIK…
Impossible when you the posts aren’t actually in the page. We load only 10 ~ 20 posts each time to keep payloads small and the page fast.
Oh. That’s right. That would make it impossible.