Are your website pages full of phrases such as “look in the right column” or phone numbers without area codes so they’re not easy to dial on a mobile device? Are your page’s text layouts, tables, and images optimized for both desktop and the responsive move to mobile? With 70 percent of students (and growing) now reporting they look at college websites on a mobile device, we know higher ed web teams must be guided by a “mobile-first” approach to designing new pages and maintaining existing ones. As you’ve made the technical changes necessary to maximize mobile, have you put the same emphasis on content? In this content-focused session, you’ll learn how to get buy-in for a consistent mobile-first philosophy from both top administrators and your page maintenance constituents. Learn real-world examples of how to track down non-mobile friendly content and make adjustments. Plus get ideas on how not to sacrifice the larger capabilities of the desktop web world at the altar of the mobile-first mantra.

Notes:

• You can never get it 100% the same using MAMP
• Vagrant / VVV / VV
  • Multiple sites on a single vagrant instance
  • But a crash could take all the sites out
• Docker
  • Still virtualization. Run in sandbox that can be taken down and examined. But it runs directly on host OS
  • It is CONSISTENT. A container will run the same on any computer or OS.
  • Portable
  • Native access to the OS

Docker Terms

• Dockerfile
  • The blueprint for your container
• Image
  • Copiled dockerfile
• Container
  • Running instant of an image. 1 image can run hundreds of containers.

Local by Flywheel

• Can swap enviroments (including PHP on the fly)
• Does all find/replace for local/production
• Multisite support
• Supports WP CLI
• Site import export
• 500M download – do later

Lando

• CLI for docker