This is mostly implemented on the feature__hybrid_responsive branch now, pending testing, tuning, and merging into the v11 branch. It's working very nicely.

It's important as users will be expecting responsive design nowadays, regardless of us having a very good mobile mode.

Users will probably expect our own site to use responsive design, so it will need refreshing also.

Chris,

I am actively developing a responsive theme based off a default theme using the Theme Wizard. The design I'm using is 12-column with breakpoints at 600 and 1000px. I realize dual-breakpoints complicates the design, but I decided upon this setup as it offers more flexibility. My design is 300px up to 1920px wide.

The first change I made was to add max-width: 100%; and height:auto; to img, like this:

img {
border: 0; /* Some (older?) browsers imply a border for linked images */
max-width: 100%; /* Responsive image 1 of 2 */
height: auto; /* Responsive image 2 of 2 */
}

FYI, width: 100%; had unintended consequences as it caused other graphics to grow excessively, such as the breadcrumbs graphic.

I have quite a few other changes I've made in global.css, including customizations that wouldn't apply to developing a default hybrid responsive theme. However, I can share any of the changes I've made if you'd like to review, as some of them may be helpful.

That's great giles :)! I think the best way to proceed is I'll comment in this issue when my own git branch is done, and you can test it and suggest which rules to copy each way? A major goal for me is simplicity within the CSS, so it would be an amazing outcome to have 2 responsive options for people.

Chris, I'd love to compare your code against my own when you believe it will be helpful. Although, I make no promises I won't look before then.

When you say 2 responsive options, are you referring to 1) the Bootstrap option and 2) a more open ##column / panel option? Or do you mean 1) a panel option and 2) a ##column option?

I mean the upgraded default theme, and your theme. But it could be 3 later on, we shall see how it all plays out :).

Okay, this branch is now ready for merging into the v11 branch. Everything is tuned for responsive, including all the admin screens. Lots of improvements. Waiting on Salman to finish #508. Patrick is likely to commit into this branch for #2128 now though.