• Grid-based layout
  
• Support for responsive design
  
• Interface components (e.g. tabs)
  
• Javascript snippets (e.g. dialog boxes)
  

• Why? (i.e. problem, opportunity, etc.)
  
• Who? (i.e. audience, setting, etc.)
• Where? (i.e. context of use, devices to be supported, etc.)
  
• When? (i.e. learner intent, off-line access, etc.)
  
• What? (i.e. learner goals, organization goals, etc.)?
• How? (i.e. organizational support and capabilities,
  existing or new content, etc.)
  

• A standard IA technique - even more essential for RWD
• Inventory a first step, but prioritization is the key
• Plays a key role when deciding upon RWD breakpoints

• Performance support
  
• Informal learning
  
• Social networking
  
• Real-time coaching/mentoring
  

• What we’ve covered so far 
• Why version 2.5 was a true milestone release
• Multi-device support is now easy, but doing it well is not
• Creating a multi-device learning strategy foundation
• Responsive Web Design as a process
• “Mobile Learning” in a multi-device world
• Multi-device experience goals
• Moodle course site learner experience goals
• The real story about multi-device learning
  
• Coming up
• A guided tour of a multi-device Moodle course site

<div class="media">
   <a class="pull-left" href="#">
   Media thumbnail object
   </a>
   <div class="main-body">
      Descriptive text for media
   </div>
</div>

<div class="row-fluid">
   <div class="span6">
      Column one content
   </div>
   <div class="span6">
      Column two content
   </div>
</div>