-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The blog is a tad hard to read #25
Comments
@diasdavid I tend to agree, do you think this affects the docs in general? @akrych what should we do here? Maybe just promoting those titles to h1? Or do we rework the font properties? |
Sure :) I will propose some small corections to text, which will improve the readability of posts. |
I agree with everything except the middle-endian date format... 😛 |
I can benefit from darker+thicker fonts as well 😄 . Kinda like what github uses. It's little light to see for me. This will make more people finish through the docs. Or may be it's just me 😄 |
@kishansagathiya No I agree, I'm going to 👍 on a font change here. The font on the site is pretty hard to read. I was about to file an issue about it. |
@kyledrake awsome |
My proposition for blog/news page (I add also switch button for change to dark backgorund theme - to pepole who like read white letters on dark:) |
The issue isn't really light vs dark, I really do think the font/size is
just not very readable. I would switch to a different font or something a
little stronger. It's not necessary to make a dark theme to resolve this
(but feel free!), just a change to the font.
…On Mon, Oct 1, 2018, 7:08 AM Agatha Krych ***@***.***> wrote:
@hsanjuan <https://github.com/hsanjuan>
My proposition for blog/news page (I add also switch button for change to
dark backgorund theme - to pepole who like read white letters on dark:)
[image: cluster_website_news]
<https://user-images.githubusercontent.com/22168118/46293548-24523880-c594-11e8-8790-52b853f1c041.png>
[image: cluster_website_news2]
<https://user-images.githubusercontent.com/22168118/46293552-274d2900-c594-11e8-9682-2644a8544e42.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABt-bv6ugUQlaHfceAd3AWFKEaXhUCFks5ugiHVgaJpZM4U7OAQ>
.
|
Hello :) I know Kyle, I change font here to "Inter UI" font. The light/dark version it was my additional proposition. |
@akrych This is much improved! A few points of feedback:
For those following along at home, expand for the gist of the line length thing, from the first linked article:Having the right amount of characters on each line is key to the readability of your text. It shouldn’t merely be your design that dictates the width of your text, it should also be a matter of legibility. The optimal line length for your body text is considered to be 50-60 characters per line, including spaces (“Typographie”, E. Ruder). Other sources suggest that up to 75 characters is acceptable. So what’s the downsides of violating this range?
It turns out that the subconscious mind is energized when jumping to the next line (as long as it doesn’t happen too frequently, see above bullet point). At the beginning of every new line the reader is focused, but this focus gradually wears off over the duration of the line (“Typographie”, E. Ruder). In order to avoid the drawbacks of too long and too short lines, but still energize your readers and keep them engaged, we suggest keeping your text within the range of 50-75 characters per line. |
@meiqimichelle I made some corrections to the line line length this blog. You can see and comment it here |
We're leaning on tachyons css in our other sites and Web UI to bake in a legible typescale and nudge us to think about line lengths / measures too. |
Blocked by #46 -- but that issue is |
Something like:
The text was updated successfully, but these errors were encountered: