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
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
FoundationPress includes a bunch of navigation styling in the navigation.scss
This is special styling without any documentation. (Which causes problems for users using FoundationPress for the first time #1364)
FoundationPress is a Starter Theme is for WordPress implementing the foundation-sites framework
Because of this I don't see any reason why FoundationPress should implement own styles different to the foundation-sites standards unless WordPress requires those styles.
I recommend following changes:
Remove the unnecessary stylings in the navigation scss
Reset the Top-Bar and Menus Styling-Variables in the settings.scss
Ole, thank you for this clean WP-starting theme.
However, talking about navigation, I think it is not really good practice making the menu responsive by creating two menu locations, rendering both in the DOM, and then just set "display: none" in CSS for whichever is not necessary in the current view. There should be only one menu location in the header, as we are talking about the same functional item ("header menu") regardless of size of viewport. Then apply CSS styling with media queries to this one. This is simple to solve by using flexbox (order), but if FoundationPress needs to support legacy browsers, it is still achievable by using floats.
Also, putting the hamburger icon into title-bar and the menu into top-bar makes changing responsive menu toggling (ie. make a different breakpoint only for the menu) a cumbersome task.
FoundationPress includes a bunch of navigation styling in the navigation.scss
This is special styling without any documentation. (Which causes problems for users using FoundationPress for the first time #1364)
FoundationPress is a Starter Theme is for WordPress implementing the foundation-sites framework
Because of this I don't see any reason why FoundationPress should implement own styles different to the foundation-sites standards unless WordPress requires those styles.
I recommend following changes:
According to the Foundation Docs https://foundation.zurb.com/sites/docs/top-bar.html#advanced-layout
The text was updated successfully, but these errors were encountered: