Streaming live at 10am (PST)

Adjusting an already built site for wider browsers


#1

Hi Webflowers -

already built out my site. whole bunch o pages. site is here:

https://preview.webflow.com/preview/scottbarbey70956011502405-0cd0e7d07ed35?preview=0f56a325a84c45c5fd20d145375281af

now, looking to constrain WIDTH of site on larger monitors. Basically, happy with site on mobile, tablet and desktop... until browser is set wide and expands past 1800-2000. Thought someone had a workaround.

Looking for a solve that doesn't starting from scratch. :smile:

As always - thanks in advance.

Scott B.


#2

Okay--super simple solution:

Drag a new div block to the top of your page. Call it "wrapper" or anything you want. Set the width to 100% and the max width to 1800px (or whatever). Now go over to your navigator and drop in your existing sections/content.

Done!


#3

@McGuire -
just started and your suggestion seems to be working awesome. Resolves 99% of my problems.

Last 1%... my Nav.

I built the div to max at 1600. When I bring everything into it, all works well BUT the nav.
More specifically - the nav works fine UNTIL browser goes beyond 1600. At that point, the opened hamburger nav starts losing visibility along far right edge of browser. The wrapper div seems to be creating a mask that blocks visibility... or the nav is still trying to align to the far right edge of browser.
whichever the case, cannot figure a workaround.

to help in accessing this issue, my home page has the nav outside the wrapper div to show you how it should work beyond 1600. url is: http://scottbarbey.com

now, compare homepage to an inner page for UNIQLO/LUCKY BREAK, where I put the nav into the wrapper div - and expand your browser past 1600, to see how it gets funky. url is: http://scottbarbey.com/scott-barbey-lucky-break

as always - appreciate the help.
Thanks again -

Scott B.


#4

Your nav is not outside the wrapper div for the second link! It's actually nested right inside your wrapper div.

(Both links you provided seem to have a 1 tacked on to the end making them unusable without modifying the destination URL)


#5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.