TomShawn opened a new pull request, #391: URL: https://github.com/apache/cloudberry-site/pull/391
On a 16" screen the article column rendered at only ~760px because the docs pages inherited the 1200px `--global-main-width` shared with the marketing pages, leaving wide empty gutters on both sides while the sidebar, TOC and article fought over what was left. Docs pages now use the full viewport, capped at 1920px so lines stay readable on ultra-wide screens. The TOC moves from a percentage-based col--3 to a fixed 288px column, so every remaining pixel goes to the article instead of inflating the TOC on large screens. The article column grows to fill whatever is left. This also aligns two stale breakpoints (1440px) in the DocItem and DocRoot layouts with the 1280px breakpoint design-style.scss already uses to hide the TOC. Between 1280px and 1440px the TOC was rendered next to an article still claiming 100% width, which squeezed the TOC down to ~185px. Measured article width at 1728px viewport: 760px -> 921px. Current: <img width="3030" height="1478" alt="image" src="https://github.com/user-attachments/assets/abf1893b-dc90-4eed-b785-b290f1fc5789"; /> Refined: <img width="3068" height="1484" alt="image" src="https://github.com/user-attachments/assets/0ee2ccb1-eebd-459d-b831-53edd538a53f"; /> <!--Thank you for contributing! --> <!--In case of an existing issue or discussions, please reference it--> closes: #ISSUE_Number <!--Remove this section if no corresponding issue.--> --- ## Change logs > Describe your change clearly, including what problem is being solved or what document is being added or updated. ## Contributor's checklist Here are some reminders before you submit your pull request: * Make sure that your Pull Request has a clear title and commit message. You can take the [Git commit template](https://github.com/apache/cloudberry/blob/main/.gitmessage) as a reference. * Learn the [code contribution](https://cloudberry.apache.org/contribute/code) and [doc contribution](https://cloudberry.apache.org/contribute/doc) guides for better collaboration. * Make sure that your changes deployment preview is successful. * List your communications in the [GitHub Issues](https://github.com/apache/cloudberry-site/issues) or [Discussions](https://github.com/apache/cloudberry/discussions) (if has or needed). * Feel free to ask for the [cloudberry committers](https://github.com/orgs/apache/teams/cloudberry-committers) or other people to help review and approve. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
