The next engagement element I wanted that couldn’t actually show on my mockup was a fixed menu that follows the user as they scroll through the posts on the homepage.  This was an important functionality that I almost had to give up because fixing an element plays all kinds of havoc with the skeleton framework.  To troubleshoot this I hit up google again. This query and response on stackoverflow gave me the answer to my problem…a single non-breaking space. “I recommend that you put your logo and menu in a <nav>element. When closing </nav>, insert a non-breaking space ( ). This non-breaking space will hopefully fix your problem!”

However, Once I added the responsive nav, more conflicts arose so I tried something else.  I wrapped my nav in a div and made that div it sits in fixed instead of the nav element itself. This seemed to work too.

From:

Fixed Navigation