feat: increase content width #21
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
 This is how it looks like on my website. There is no breathing room between the left sidebar and the docs content. I suggest, we look at some docs website and then bring those improvements in |
| Screenshot from https://www.radix-ui.com/themes/docs/overview/getting-started  Screenshot from https://laravel.com/docs  Screenshot from https://tailwindcss.com/docs/installation  Screenshot from https://docs.astro.build/en/tutorials/add-content-collections/  |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Hey there! 👋🏻
This PR increases the width of the content to a
70chunit.The same was done for V5 documentation a long time ago.
I have tested the change on different resolutions, and I believe we could even increase it to
80chafter a1920pxof width. What do you think?This will also help to solve some issues brought up by #20.