Comments (5)
-1 for font size, I think it's fine and a decrease in font size wouldn't be great for people with not perfect eyesight. I suspect more of the problem with the font itself, is that it's quite thin, and it's got some very similar characters, similar to Helvetica. Try setting the font to 'Verdana' or something similar, and see how it is for you, that'd probably be my vote off of the top of my head.
+1 for limiting line length though, that would help a lot of legibility problems, although, I have the docs in a 1/2 width window anyway so I can reference them while coding, so this isn't as much of an issue.
from grav-learn.
I'm all for accessibility, but I think it's a bit backwards to measure the default font-size after someone who has poor eyesight. As a user it's easy to increase the font-size if I need it, but the default ought to be size that's as legible as possible for someone with normal eyesight, IMO. For reference, 14px
is what Wikipedia uses for its body text.
I agree that the font maybe isn't optimized for readability at 14px - primarily due to its low height - but I still think the size is more of an issue than the font itself.
from grav-learn.
Any thoughts on this? I really think it would make the documentation more easily digestible. Technical documentation has to contain a lot of text, and you want the visitor to be able to get a good overview at a glance – a lower font size would definitely help with that!
from grav-learn.
https://medium.com/@xtianmiller/your-body-text-is-too-small-5e02d36dc902
just read this today, and it makes some very valid points about making the fonts LARGER !!!
I'm not sure there will ever be one size that fits all, that's why you can CMD + or CMD - in your browser to suit your needs.
Regarding width, again, you can resize your browser to make the fonts fit to the size you want exactly. No point hardcoding that for one person's preference.
from grav-learn.
Even the article you linked argues that larger font sizes only increase readability if the content has been tailored for such use cases. I would argue that technical documentation isn't necessarily that kind of content.
But leaving nitpicking aside, what I'm really looking for is to make it easier get a good overview of the different articles in the docs. The theme variables article is an excellent example of a page that's difficult to get an overview of, but where an index or a succinct list of the main variables might be very beneficial. Maybe lowering the body font size won't give a good overview just by itself, but it's one step to consider in how to enable people to get a good overview of the docs in a glance. I think heavy Grav users will benefit immensely from this.
If we could get one concrete change out of this issue though, maybe it could be that we add a max-width
style to documentation pages? While font size may be more influenced by subjective opinions, it's widely established that it's more difficult to read too long rows of texts. For instance, this Smashing Magazine article claims that 45 to 75 characters per line is optimal for readability (and Medium's design is an excellent example of a place where this has been implemented)
from grav-learn.
Related Issues (20)
- Manual for Azure PaaS is outdated HOT 1
- Missing images in accounts docs
- Undocumented property `value_type` in Array field HOT 1
- Revere proxy
- Terminology Mismatch in Grav-Learn
- `Section` blueprint form field mistakenly lists `title_level` attribute
- Blog tutorial doesn't say how blog items are added or formatted
- 02.content/01.content-pages it is broke
- Remove ATOM editor
- Cookbook: per-site configuration of robots.txt does not work
- https://learn.getgrav.org/17/admin-panel/accounts is missing all PNGs HOT 1
- Functions PCRE (regex?) error HOT 2
- Add user/cli folder to Folder Structure section in Basics chapter
- multisite-setup, setup.php `plugins` key does not allow disabling plugins HOT 4
- http://twig.sensiolabs.org/ links not working in 'Step 4 - Base Template' HOT 1
- The search box is not accessible and functional HOT 1
- The nonsensical section appears behind the footer HOT 1
- Exception thrown for 'js_module_pipeline' in local install HOT 2
- Media "sizes" doesn't render properly with markdown syntax
- Modular documentation not clear (at least for me)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grav-learn.