from the if-at-first-you-don't-succeed,-avoid-skydiving-or-making-immediate-changes-directly-to-live-systems dept.
[2020-03-21 15:06:00 UTC: Update 1:
(1) Reminder: this has so far been implemented only on our *development* server (https://dev.soylentnews.org/); it has NOT yet been rolled out to this (the production) servers.
(2) The control (now a simple text link, no longer a button) no longer defaults to taking up a whole physical line immediately above the first comment.
(3) Please note that in certain corner-cases, it is possible that screen size limitations may cause an overflow onto the next line.
(4) And the control should now appear aligned-right in the story header. =)
[2020-03-21 15:42:00 UTC: Update 2: Fixed typo in the first of the above two links to our dev server. --martyb]
This is a follow-up to: Changing the Site UI to Making Long Stories Easier to Navigate -- Input Requested.
Wow! Thanks for all the positive feedback to the previous story! I knew the implementation was a bit rough around the edges, so I very much appreciate the positive, constructive feedback that was provided!
Based on your input -- primarily displeasure in having a single button take up a whole physical line -- I have modified the in-memory template on our development server to now provide a textual link in the story header right after the printer icon. It should only appear when viewing the story by itself; there should be no indication of this on the main page.
To repeat, this is only on our development server so far; it is not yest implemented on our production server (i.e. what you see here).
In short, should this get rolled out to production?
- Yes, with these suggested changes.
Please refer to the previous story (linked above) for test scenarios and reply with any issues you may find!
[20200320_184315 UTC: Update: Made the dept. line longer to better demonstrate space [un]availability.--martyb]
[20200320_202305 UTC: Update: Added topics: "/dev/random", "Code", "Software", and "Answers" topics to better illustrate their use of space in a story. --martyb]
[20200321_175412 UTC: Update: superseded by: Skip to comment(s) -- Second Try --martyb]
First: Please accept my best wishes to everyone during SARS-CoV-2 / COVID-19 / Coronavirus pandemic. Please take all necessary precautions to keep yourself and those around you safe!
Second: I should not have been surprised, but I must confess my admiration at how the SoylentNews community came together in support of each other in response to SoylentNews Community -- How has SAR-CoV-2 (Coronavirus) / COVID-19 Affected You? As of my writing this, there are over 300 comments! community++ This is what I had hoped for when SoylentNews started over six years (Wow!) ago, and so validates my giving of my time to this site!
Third: (and the focus of this story) our virus roundup stories are... long. An AC posted a comment: thanks to eds:
Thanks editors for pulling together this summary. SN for the win!
One comment--it is kind of long to scroll down through, to get to the comments. Perhaps next time some of the longer stories could be put inside the spoiler tag?"
This was quickly acted on by a member of staff, but that was not universally embraced as a "Good Idea". Both Soylentils, to my eye, had good points. If I am visiting an active story again, I have already read the story (both the "Intro Copy" and the "Extended Copy"). Why should I have to scroll through a wall-of-text to get to the comments? The suggestion of using <spoiler>...</spoiler> to bracket the contents of each of the merged stories seemed like a reasonable suggestion. But, when you have a hammer... Right idea, but maybe not quite the right tool.
Aside: If I am reading a review of, say, a movie, then a spoiler is an appropriate way to hide plot details from those who have not yet seen the movie. That is not the situation here. Why hide details of a story about the pandemic? Hmm. A good first try, perhaps, but it looks like we need something different in this case.
Idea: what if there were, say, a button at the top of the story that I could click and be brought immediately to the comment section of a story? Hey! I can do that!
Acknowledgements: At this point, I hereby express my sincere thanks to AndyTheAbsurd for constructing some CSS which allowed the conditional display of a button, and to FatPhil for his testing efforts. Thanks guys!
Read on past the break for details on the implementation and a request for assistance before I attempt to roll it out to production.
[2020-03-23 01:32:11 UTC Update 1:Ed. Note - updated to clarify location of the skip to comments button.--fnord666]
[2020-03-23 12:56:40 UTC Update 2: Changed link target from "#acomments" to "#commentwrap" per suggestion in: https://soylentnews.org/meta/comments.pl?noupdate=1&sid=36704&page=1&cid=974278#commentwrap; added "Note-to-self". --martyb]
Thank You! Thanks to everyone who provided feedback on a new UI feature to the site; [Skip to comment(s)]" is now live on SoylentNews!
The SoylentNews' Main Page should function and look the same as before. The magic manifests only after a specific story has been opened. Code has been added to a site template so that "[Skip to comment(s)]" should now appear, right-justified, in the first of the two lines in the title bar that appears immediately below the story's title.
[Note to self: see in-memory version of template: "dispStory;misc;default" original implementation target fragid of "#acomments" changed to "#commentwrap" as of 2020-03-23 12:56:40 UTC--martyb]
Clicking the button will bring you to the comment header block. (That's where you can adjust Breakthrough, Threshold, and Threading preferences (either one-time-only, or save it away, permanently.)
Quite frankly, thanks to the community's feedback, it looks and behaves better than what I had originally envisioned!