You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At certain screen resolutions, the page feels off-center. This is due to the ragged-right (and thus larger) margin of the cycle image vs the tighter hard left edge of the logo/subheader area. End result is a small left margin and a large right margin. I think the page should be placed in a fixed width container that grows/shrinks along certain set breakpoints, but I'm open to other solutions.
2. Equilateral triangle of screenshots loses equilateral-ity as page stretches
As the page widens, the two bottom screenshots move outward, but the top screenshot does not move upward (or, more accurately, the cycle graphic doesn't move downward) and the balance of the hero is lost. This is more easily fixed if my proposed to solution to the first item above is enacted, but it could totally be mathed out with some SCSS (and mayyybe some JS?) so that it moves and stretches equilaterally.
Another potential solution suggested by @arbitrarynoun is responsively larger screenshots.
The text was updated successfully, but these errors were encountered:
1. Off-center Homepage
At certain screen resolutions, the page feels off-center. This is due to the ragged-right (and thus larger) margin of the cycle image vs the tighter hard left edge of the logo/subheader area. End result is a small left margin and a large right margin. I think the page should be placed in a fixed width container that grows/shrinks along certain set breakpoints, but I'm open to other solutions.
2. Equilateral triangle of screenshots loses equilateral-ity as page stretches
As the page widens, the two bottom screenshots move outward, but the top screenshot does not move upward (or, more accurately, the cycle graphic doesn't move downward) and the balance of the hero is lost. This is more easily fixed if my proposed to solution to the first item above is enacted, but it could totally be mathed out with some SCSS (and mayyybe some JS?) so that it moves and stretches equilaterally.
Another potential solution suggested by @arbitrarynoun is responsively larger screenshots.
The text was updated successfully, but these errors were encountered: