course on base themes in Drupal. • Applying responsive principles to Drupal sites. • Case study #1: responsive retrofit • Case study #2: using Fusion • Awesome give-away
the standard API for older browsers (e.g. for media queries, border radius, etc). • respond.js • adapt.js – doesn’t serve stuff until it can be used by the browser (good for bandwidth) • modernizr
still working on what a “best practice” is. • Typically a JS script determines screen size and reports back to the server. • Server then gives predetermined “low bandwidth” content. • However, small screen doesn't always mean “low bandwidth.” It's just easier to make that assumption. • e.g. http://drupal.org/project/responsive_images
down politely. • The technology is harder because of our expectations of delivering perfect content. • By using existing libraries we can provide an acceptable experience to browsers that don't support modern tech.
improved theming defaults over Drupal core. • If your base theme doesn't improve Drupal, it's not the right base theme for you. • http://www.designtotheme.com/blog/base-themes
with Zen Grids for maximum efficiency. • NineSixty is my go-to theme for quickly banging out just about any theme. • Fusion is my go-to theme when I will be handing off the site to someone else to maintain who is tech savvy and may need to update the layout later on.
• Identify content break points. • Determine page element characteristics for each new width. • Bonus: allocate time for retrofit based on visitor stats.
of page. “Beauty” is not a page goal. (And if it is, you’re doing it wrong.) • Audit the content on the site. • Identify content break points. • Determine page element characteristics for each new width. • Bonus: allocate time for retrofit based on visitor browser stats.
you display on the site. • Make a spreadsheet if you have a big site. • If relevant, note the contextual relationships of content pieces (e.g. user picture + video submission).
because you have real content. • Use content, not device sizes, to determine break points. • Stretch / expand your browser to find where the design “breaks”.
up the media queries in your new CSS file. @media screen and (maxwidth: 960px) {} • Assign new properties and values for containers, fonts and navigation.
Uses more than just regions for layout. • Uses “skins” to alter the properties of blocks for layout. • Most configuration done through the admin interface. • Well documented.
love their team of developers. • The skins are great for clients who want to extend their site. • They don’t rush to market with the latest feature. They get it right the first time.
four layouts. • Context-aware forms. Need to add responsiveness for rich media. • Supports older browsers with polyfill css3- mediaqueries.js • Focuses on “show all” approach, so there are no hidden elements eating up bandwidth.
only screen and (max-device-width: 1024px) and (orientation:landscape), only screen and (min-width:960px) and (max- width:1199px) and (min-device-width: 1100px) • Tablet (portrait) only screen and (max-device-width: 1024px) and (orientation:portrait), only screen and (min-width:768px) and (max-width:959px) and (min-device-width: 1100px) • Mobile only screen and (max-width:759px) • These can all be easily adjusted in the UI.
tablet. • The mobile layout is linearized. • You can choose the position of the sidebars through the UI for each of the layouts. • With additional CSS you might want to collapse / linearize regions for the the tablet – portrait display.
are made for mobile-friendly navigation. • You can make these adjustments based on the Domicile retrofit. • Or look at the beta superfish options for touch-friendly navigation.