-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Make it easier to customize menus #107
Comments
👍 |
@tilomitra and have no differences between primary, secondary, breadcrumbs, ... navigations. |
I expect a horizontal menu independent of YUI. |
@okuryu Are you talking about a horizontal dropdown menu? |
@tilomitra Yes. Because dorpdown menu depends on |
My implementation that addresses this bug is here: #142 |
Whoops, closed by mistake. |
Thought this might be the best place to ask a basic question about Pure. |
@jake905 Hello, Jake 🍎. |
See #424 (New Menu for 0.6.0) |
I guess I can close this issue, as I've ended up doing just what is discussed here. "New Menu" is out there (at least on http://stage.purecss.io) in the RC (release candidate) for Pure 0.6.0. It's certainly easier to customize. The YUI connection has been cut. I'm sure there will be new issues, questions, and proposed enhancements, but we can file those as new GitHub issues. |
In this example I have tabs like Home, About Us, Services, News & Career. You can add or update tags as you want. This menu is supporting sub menu feature. Under About Us & Services I added some sub menu items for demo purpose. Technically to design this horizontal menu I used UL element of HTML. Using pure CSS I am defining color & theme to the menu. For responsive I used CSS3 media queries. In media query I configured the menu max-width to 750px. 750px is nothing but the total width of my horizontal menu (including all tabs)... https://goo.gl/VwTusI |
Styling menus are a pain. I would love to have it be as simple as styling buttons (basically, needing to go off only one element to style it). One of the reasons it's painful to style is because the styles and the DOM tree were initially borrowed from Y.Menu.
I propose starting from scratch to see what the simplest possible DOM structure would look like for a menu, and then think of JS integration. I think a simpler DOM + less class names + less direct descendent selectors would make menus easier to customize.
The text was updated successfully, but these errors were encountered: