audio stimulates your users’ minds, giving them something more than text to dig through, and a reason to come back. • Media breaks up the text, improves the flow, and makes a long post seem much shorter and more enjoyable to read. • Maybe that is the whole point of your site! (*cough* membership sites *cough*)
Some browser don't support even the *most* popular formats. (Even Chrome and Chromium aren't equal). – More formats means more effort. • Time, hosting, code, etc. – HTML5 spec is still in flux. • Lots of vendor-specific implementations & hacks.
which browsers support which containers and codecs. • If you want maximum compatibility you have to use licensed codecs. • Two letters: IE – <= IE 8 – Nope! – IE 9 – User must install compatibility plugins • Copy protection is not dealt with in HTML5, so if you need DRM out of the box you're out of luck. • After all is said and done you might *still* have to use Flash.
Make another version that uses H.264 baseline video and AAC “low complexity” audio in an MP4 container. 3) Make another version that uses Theora video and Vorbis audio in an Ogg container. 4) Link to all three video files from a single <video> element, and fall back to a Flash-based video player.
MediaElement.js library. • Uses consistent HTML markup, so it's super easy to use CSS to skin the players. • Can swap out default MediaElement.js support via 'wp_video_shortcode_library' filter. • Easy insertion via new post formats UI. • Additional metadata extraction via getID3 library.
images that are *way* bigger than they need to be. • Furthermore, you're serving lots of images at the bottom of posts that might not even been seen by your users. • That's a lot of bandwidth to waste! • Also slow!
content into your WordPress site. • Just paste a supported URL is on its own line. • Optionally wrap URL in the [embed] shortcode. – It also allows you to set a maximum (but not fixed) width and height, like so [embed width="123" height="456"]...[/embed] • For security purposes, WP only embeds URLs matching an internal whitelist.
oEmbed discovery is disabled by default. • You can get around this though! – Install Enable oEmbed Discovery plugin. – Gives unfiltered_html users (Administrators and Editors) the ability to embed from websites that have oEmbed discovery tags in their <head>. • Caveat administrator.
Acts on images in posts, pages, and featured images (post thumbnails). To start using Photon: • From the Jetpack page in your blog dashboard, click 'Activate' button for Photon. • You’re done! http://jetpack.me/support/photon/
Step 2: Sign up with your favorite CDN. – MaxCDN – EdgeCast – Amazon Cloudfront • If media is a big portion of your site this is not something you should skimp on! (It's okay to pay for important things)