It is traditional in responsive design to stack major sections of the page layout when the viewport falls below a certain width. When following a cookie cutter content heirachy this means throwing the sidebars below the main content container.
It's pretty common in web design to utilise the rule of thirds. Important information or calls to action are commonly place in the final third of the page, historically this has been a natural resting point when scanning the page.
We take advantage of this on many pages of drupal.org, a good example is the new events page on g.d.o
Action
Split the sidebar region into two regions; one contains important information, the other is less important. On a desktop layout the regions will be stacked on top of each other and will look identical to the current design.
On smaller screen, we will be able to stack our important information above the main content region and our less important information below. Yay!
Comments
Comment #1
drummComment #2
LewisNymanIs this already done in 2.x-dev? See #2226213: Split the right sidebar region into stacked 'Major' and 'Minor' region
Comment #3
drummIt may have been. It looks like the
sidebar_first
region is the more-important region. It could use some testing.Comment #4
LewisNymanIs there an environment I can test this? I remember testing this at dev days.
Comment #5
drummdrumm-drupal.redesign.devdrupal.org or rwd-drupal.redesign.devdrupal.org are okay to test on now.
Issues like #2397869: Move the issue metadata to the top in markup need good notes on what blocks to move, and any other changes, in the issue summary.
Comment #6
LewisNymanGreat, I can make these notes. I just need a login on https://rwd-drupal.redesign.devdrupal.org/user that has access to blocks
Comment #7
drummhttps://www.drupal.org/node/1018084 has instructions for logging in as any user on any dev site. Let me know if something is wrong with your SSH keys.
In the meantime, I deployed a fresh dev site, https://responsive-drupal.redesign.devdrupal.org. That will be even closer to Drupal.org's current state.
Comment #8
tim.plunkettTempted to bump this to critical.
Why bother have issue metadata and jump links at all if they're below ALL of the content on mobile?
#2397869: Move the issue metadata to the top in markup
Comment #9
drummI tried this out on https://staging.devdrupal.org/node/2444211, and the block mostly works. #2397869: Move the issue metadata to the top in markup has specific CSS cleanup that is needed.