Comments (2)
Personally I don't like it when documentation fills up my whole screen. I like being able to use a huge monitor for more than one thing at a time, which is especially useful when you're working on something in a terminal and also referencing the docs at the same time.
Reading paragraphs stretched across a page also hinders readability. It means your eyes have to travel farther from the end of one line to the beginning to the next, and you could end up on the wrong line. It can also end up feeling a bit like this:
Also, we do use that whitespace when there's actually something to put there. For example, most of our reference pages put examples alongside the content:
Sure, on some pages it can look like a lot of wasted space. We could maybe fill it in with the grey background that we use for pages that have example content for the margins. That would at least make the text feel cushioned by something.
We could also make the main column a tad wider, we'd just have to be careful not to make it so wide that we can't have example content in the margins anymore (it'd be a shame to wrap it on common laptop resolutions). To me it doesn't really seem worth it, to be honest.
In any case, please try to not sound so dramatic and abrasive when giving feedback. Consider the humans on the other side of the screen. Calling someone's website awful (especially for such a minor concern) is not very nice. This is not the first time we've had to warn you about how to communicate feedback effectively.
from docs.
from docs.
Related Issues (20)
- `fly -t tutorial builds | grep check` doesn't return anything. HOT 1
- CONCOURSE_POLICY_CHECK_FILTER_HTTP_METHODS is wrong HOT 2
- Switch our docs to use a fork of booklit
- Consider a better separation between different users and tasks, concepts, and references? HOT 7
- Small typo ran -> run
- Failure when going through the tutorial and trying to access localhost Concourse HOT 8
- Document syslog format
- Update prometheus metrics list
- Update docs for fewest container placment strategy
- tutorial-inputs-outputs.html has broken iframe HOT 1
- Broken link on the Job & task hooks example page HOT 1
- Where is the instruction for TLS configuration?
- Rename Job Documentation improvement
- Blog is offline due to certificate problems HOT 2
- [Docs] Is there a way to generate a book for it? HOT 3
- Update docs with Concourse hermetic feature
- Fly CLI docs are incomplete HOT 1
- Pipeline naming standards not documented
- "Building and Pushing an Image" wrong put parameter
- Hard Dependency on iptables, Unable To Start on Fedora 38 Host HOT 1
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 docs.