-
Notifications
You must be signed in to change notification settings - Fork 7
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
Responsive design #7
Comments
Can we please use the SCSS version of bones? It's much easier to work with than plain old CSS. |
I picked css because it's more universal to work with when you have people from a variety of different backgrounds. I can't justify working with a preprocessor in this case even though that's the way I prefer to work. |
What are the odds of someone willing to do all this work but won't put up with a preprocessor? |
Odds are high as I'm the one that's willing to do the work and not willing to put up with a preprocessor. Look, I really appreciate the argument you're making, but the barrier of entry to contribute to this project has to be as low as possible. If you would like to use sass or scss please feel free to do so and upload the css or create a branch where these files exist. Just realize that someone may come along that doesn't know any better and overwrite the css and cause a lot of headaches. |
hi Mike, |
No one is doing it yet. Definitely needs to be done. Your help would be greatly appreciated. I would love to see something like this: http://responsive-nav.com/ as far as functionality. It doesn't have to use that plugin, though. |
I'll try take a look tonight. On Mon, Nov 25, 2013 at 1:46 PM, Mike Garrett [email protected]:
|
Yeah, I'm looking into it now. Sent from my iPad
|
It might need some styling love, but that could be a separate ticket? (I only see a hyperlink when I hit that breakpoint) |
Yeah, I wasn't sure if we wanted to make a hamburger button or something a little nicer looking so I just left it at the default for now. |
Most of the responsiveness is handled already. We need a mobile-friendly menu, a couple breakpoint changes (what if we get rid of the table markup for smaller screens?) and some QA on various devices.
The text was updated successfully, but these errors were encountered: