镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Improve doc readability #919

Description

@octref

This is how the doc looks on my 15 inch RMBP using half screen. Can't even show a full function definition.

Please improve your media queries or font-size. I'm not a mobile user.

image

Activity

  1. phillipj commented on Sep 26, 2016

    @phillipj
    Member

    I can confirm this doesn't look optimal on a retina macbook atm. This is the caused by a media query I assume is supposed to be targeting iPad-ish devices.

    @media only screen and (max-width: 1024px) {
      #content {
        font-size: 2.5em;
        overflow: visible;
      }
      ..
    }

    https://github.com/nodejs/node/blob/master/doc/api_assets/style.css#L463

    I don't have a iPad (retina or not) at hand, so I haven't been able to test if the big font size is neccessary on those devices.. It maybe time to re-visit some of these media queries.

    /cc @nodejs/documentation

  2. Fishrock123 commented on Sep 27, 2016

    @Fishrock123
    Contributor

    Looping myself in, I had a go at working on some if the CSS the other week, but didn't finish it yet.

  3. phillipj commented on Oct 18, 2016

    @phillipj
    Member

    @Fishrock123 guessing that work ended up in nodejs/node#8811?

  4. Fishrock123 commented on Nov 8, 2016

    @Fishrock123
    Contributor

    No sorry, that was for something else. This persists I'm pretty sure.

  5. diagramatics commented on Jan 2, 2017

    @diagramatics
    Contributor

    Considering that the font-size could go from 25px to as high as 35px on a portrait oriented iPad, I agree this could be overkill. I'm pretty sure the default size of 18px would already suffice on an iPad, if not, probably just a small bump to 21px.

    We could just remove the media queries completely. If that's the verdict I can go and change it.

  6. octref commented on Mar 5, 2017

    @octref
    Author

    I'm glad to find out changing a few css lines would take more than half a year.

    Seriously. Just changing the font-size to 1.6em and it'll look much better.

    image

  7. gibfahn commented on Mar 5, 2017

    @gibfahn
    Member

    @octref care to submit a PR?

  8. octref commented on Mar 5, 2017

    @octref
    Author

    Not really, and I don't have an iPad to test if the website would look good on iPad (seems the original intent for this media query is to do so).

    But it's really just change the value here https://github.com/nodejs/node/blob/master/doc/api_assets/style.css#L490 and make sure it's good on iPad.

  9. gibfahn commented on Mar 5, 2017

    @gibfahn
    Member
  10. bnoordhuis commented on Mar 5, 2017

    @bnoordhuis
    Member

    I'm glad to find out changing a few css lines would take more than half a year.

    You don't get to use that tone. Most people here are volunteers so pipe down.

  11. octref commented on Mar 5, 2017

    @octref
    Author

    I apologize. I wish the usability of the doc website can be given more attention and improved, but I could have said that in a less entitled way.

  12. bnoordhuis commented on Mar 5, 2017

    @bnoordhuis
    Member

    No worries. Reading back what I wrote, I could have voiced it in a friendlier way too.

  13. fhinkel commented on Mar 9, 2017

    @fhinkel
    Contributor

    Fixed in nodejs/node@7c8bbe3. Looks like I don't have permission to close issues in this repo 🤔

  14. octref commented on Sep 15, 2017

    @octref
    Author

    Just pinging people in this thread, this issue hasn't been resolved for a whole year.

    How it looks on half of my 15 inch macbook screen today:
    image

    Relevant CSS:
    image

  15. thefourtheye commented on Sep 15, 2017

    @thefourtheye
    Contributor

    I think nodejs/node#15430 is related.

  16. octref commented on Oct 3, 2017

    @octref
    Author

    @bnoordhuis This bug just passed its one year birthday. I don't know what tone should I use to express my frustration. I use this layout everyday and nodejs.org/api has been unusable for me for a whole year.

    image

  17. lpinca commented on Oct 3, 2017

    @lpinca
    Member

    @octref see nodejs/node#15660.
    All I can suggest is to get you hands dirty if you want to improve things.

  18. octref commented on Oct 3, 2017

    @octref
    Author

    @lpinca OK I’m glad there is ongoing effort in fixing this. Thanks for linking the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions