-
Notifications
You must be signed in to change notification settings - Fork 17
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 CSS: Goals and long-term planning #132
Comments
I'm happy to look into this. I can't give a good estimate now, but in a few hours I'll poke around and give my impression. My initial feeling is that this is doable before release. |
Yeah, I was hoping that we could add basic bootstrap styles to all the templates and only serve the core bootstrap CSS to clients we can identify as being mobile. My thought was to keep the same view templates for mobile and desktop without breaking the existing desktop CSS. I'm not sure if that plan would work though, just an idea. --James
|
Bootstrap is mobile first by default, though, so it should work regardless. Any modern CSS grid system will use media queries and sane defaults, so I think, personally, conditionally-served CSS is unnecessary (though maybe within the context of this project it is?) I forgot, I made this a long time ago using the existing markup plans had at the time, and so assuming the media-viewport tag is there (and I used some jquery for the menus I think), responsive styles are easy enough to add, even with just one media query. I'm sorry, also, I didn't really do a good job looking into this last night - I will give myself the upcoming weekend to investigate, if that's ok. |
After discussing this with a bunch of people, I've come up with a rough plan of action. I've opened a new milestone to track these steps and will be breaking out the specific tasks into tickets there. I think I'll leave this open as kind of a place for general discussion, at least for a while. Here's the game plan, in order:
|
Short-term goals:
Long-term goals (maybe? not set in stone):
Current status:
The HTML & CSS is mostly the same as in the PHP version. So far the only work I'm aware of was #86/#89. We've decided to drop the old interfaces (#92), so thankfully the only interface HTML we'll need to work with is Postmodern.
Previous work in PHP was documented in grinnellplans/grinnellplans-php#179.
The text was updated successfully, but these errors were encountered: