Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
Meta
posted by martyb on Friday March 20 2020, @03:00PM   Printer-friendly
from the putting-our-heads-together-from-a-distance-seems-like-it-should-be-easy-but-it's-MMMMMMMMMMMMMM-not! dept.

[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.

So, I hacked up something that I hope addressed the initial concern: "kind of long to scroll down through". I'll be the first to admit the implementation is crude. We can go for pretty later. (The perfect is the enemy of good enough, right?) I think the ideal would be to have a separate nexus for virus-related stories. That way we would not feel compelled to gather a bunch of story submissions into a single story. We could process each submission independently and release each on its own. Unfortunately, there is much more to it than just adding an entry to the site DB.

It has been implemented on our development server: https://dev.soylentnews.org/ and I hereby solicit feedback from the community on how well it works. It was implemented with one addition to an in-memory copy of a single site template (dispStory;misc;default).

For the curious, see Original and Updated Versions of Template: "dispStory;misc;default" ("Skip to Comment(s)" button), but do be aware that rehash replaced tabs with spaces, so what you see is NOT an exact copy of the sources.

Now what? Feedback! This is your site. I am well aware there are Soylentils who have a much better grasp of HTML and CSS than I do, and am hereby soliciting supportive feedback.

Test scenarios:

  1. Does the "Skip to comment(s)" Button not appear on the main page?
  2. Does the "Skip to comment(s)" Button appear on the story page?
  3. Does it work?
  4. Is the appearance consistent across all of the available themes?
    1. Site Default
    2. BadA55
    3. Chillax
    4. Grayscale
    5. Black IcIcle
    6. Night Mode
    7. NV
    8. OMG PWNIES
    9. SoylentNews
    10. Vomit
    11. VT100
    12. VT220
  5. Is the layout consistent other homepage settings?
    [] Simple Design
    Simplifies the design of Dev.SN to strip away some of the excesses of the UI.
    [] Low Bandwidth
    Reduces the size of pages for people with slower network connections
    [] No Icons
    Disable topic icon images on stories.
  6. Which of the preceding homepage settings would be better served with just a simple anchor?

    <a href="@acomments">Skip to Comment(s)</a>

  7. Other, what did I miss?

Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by martyb on Friday March 20 2020, @09:49PM (5 children)

    by martyb (76) on Friday March 20 2020, @09:49PM (#973643) Journal

    If I could have my wish list, you would include hidden "skip to story" and "skip to comments" links at the very top of the document, use the semantic tags, and follow the other accessibility guidelines.

    I *might* be able to hide "Skip to story" and "Skip to comments" as non-displayed links...

    <div style="display: none">
        <a href="#wide">Skip to story</a>
        <a href="#acomments">Skip to comments</a>
    </div>

    Something like that?

    P.S. I cannot make any promises, because the code is broken up in, well, interesting ways. It is based on a Model View Controller [wikipedia.org] design. I am actually a bit surprised I could shoehorn the button in at all!

    --
    Wit is intellect, dancing.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Saturday March 21 2020, @01:50AM (4 children)

    by Anonymous Coward on Saturday March 21 2020, @01:50AM (#973707)

    Wow. That was fast. Thanks for adding it. Either that or it added there since I last complained and I got too used to ignoring all the boilerplate before the stories and comments!

    • (Score: 2) by martyb on Saturday March 21 2020, @02:30AM (3 children)

      by martyb (76) on Saturday March 21 2020, @02:30AM (#973716) Journal
      As much as I would like to take credit, I made no changes, so must have been there all along!
      --
      Wit is intellect, dancing.
      • (Score: 0) by Anonymous Coward on Saturday March 21 2020, @02:48AM (2 children)

        by Anonymous Coward on Saturday March 21 2020, @02:48AM (#973723)

        No seriously, it is a big help to not have the navigation and boilerplate read to me before everything. Maybe it has been there the whole time. The three links seem to be on there whether the anchor on the page exists or not. I may have just ignored them because they weren't marked clearly and come after the link elements before the main site link. I must have just thought they were a part of the links or something. Thanks to whomever took accessibility seriously for that. It is a nice change compared to the usual reaction I get here.

        • (Score: 2) by martyb on Sunday March 22 2020, @02:58PM (1 child)

          by martyb (76) on Sunday March 22 2020, @02:58PM (#974140) Journal

          I have a friend who is legally blind and she has made me aware of some of her on-line accessibility challenges, so I am sensitive to the issues. FWIW, she tells me she uses JAWS [freedomscientific.com]. She has partnered with a non-profit agency in the area which has made it available to her. (Note: it is Windows/DOS specific). See also, these pages on Wikipedia: Screen reader [wikipedia.org] and List of screen readers [wikipedia.org].

          I would suggest reaching out to community, county, and state agencies -- many can provide grants or and other sources of support. Consider grants and work-in-kind relationships that may provide free/reduced-cost access.

          Good Luck!

          --
          Wit is intellect, dancing.
          • (Score: 0) by Anonymous Coward on Monday March 23 2020, @02:11AM

            by Anonymous Coward on Monday March 23 2020, @02:11AM (#974287)

            I appreciate your response. I have a good setup already, including a couple of screen readers, that works for the vast majority of websites I use. It is just the little quality of life things that can make a big difference. For example, while not perfect, the IRS website is an accessibility dream. Use a text-mode browser or NVDA (which is free on Windows) or Orca on Linux or AVO on Mac. Try that one and then compare your experience with SN and you'll probably see what I mean about the little things making a big difference.