Skip to content
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

Add responsive breakpoints #18 #52

Merged
merged 1 commit into from
May 3, 2022
Merged

Add responsive breakpoints #18 #52

merged 1 commit into from
May 3, 2022

Conversation

oneiros
Copy link
Collaborator

@oneiros oneiros commented May 2, 2022

First attempt to solve #18. With this change you should have a considerably larger usable area on modern wide screens.

A bit of background:

Bootstrap is a "responsive" CSS framework, which means the width of the layout containers depends on the screen resolution. Bootstraps defines a couple of "breakpoints", pixel-widths of the browser's visible viewport. At those breakpoints, widths and other CSS attributes may change. You can easily see this, when making your browser window narrower. Things stay the same for while, but if you reach a certain window width, something changes.

We use Bootstrap 4, which defined 1200px as the largest breakpoint. So if your browser window reaches a width of 1200px, the layout containers have their maximum width. With modern screens usually offering a (virtual) pixel width of 1920, this leaves a lot of screen space unused.

Thus, Bootstrap 5 introduces another breakpoint at 1400px. I copied this, but also introduced yet another, even larger breakpoint at 1900px.

I think this works really well. Please have a look.

There is also an alternative: Instead of fixed-width containers that depend on breakpoints, Bootstrap also offers "fluid" containers that always use the maximum width available. Let me know, in case I should give this a try as well.

To better make use of screen real estate on larger
resolutions.
@rwaffen rwaffen merged commit 7e44191 into main May 3, 2022
@rwaffen rwaffen deleted the issue-18 branch May 3, 2022 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants