-
Notifications
You must be signed in to change notification settings - Fork 13
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
Improvement: Increase the width of the main text window in sphinx-needs layout #51
Comments
There are pros and cons for a bigger width of the content area. One of the main aspects is, that lines containing more than xxx characters are hard to read and follow. Your screenshot shows a really wide screen, I guess something near QHD. So for me, the goal of documentation is not to fill all the white space, if it gets shown in fullscreen mode, but to be easily readable. Like in newspapers, which also have their text in multiple, even less wide, columns. But these are just my 2 cents, and I'm open to increasing the width. |
The width of the content gets increased. The left sidebar does not show a scrolbar anymore, if the documentation tree fits in the avaialble space. Issue-ref: fix eclipse-score#51
The width of the content gets increased. The left sidebar does not show a scrolbar anymore, if the documentation tree fits in the avaialble space. Issue-ref: fix eclipse-score#51
The width of the content gets increased. The left sidebar does not show a scrolbar anymore, if the documentation tree fits in the avaialble space. Issue-ref: fix eclipse-score#51
The width of the content gets increased. The left sidebar does not show a scrolbar anymore, if the documentation tree fits in the avaialble space. Issue-ref: fix eclipse-score#51
Important
Make sure to link this issue with the PR for your improvement.
Currently the part in the middle of the window with the main text is not sufficient wide and the left part is too large. Please adapt the layout, that the left part gets smaller and the one in the middle larger.
The text was updated successfully, but these errors were encountered: