{"id":14295,"date":"2015-08-25T23:35:48","date_gmt":"2015-08-25T23:35:48","guid":{"rendered":"http:\/\/make.wordpress.org\/core\/?p=14295"},"modified":"2015-09-05T15:26:13","modified_gmt":"2015-09-05T15:26:13","slug":"responsive-image-support-update","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2015\/08\/25\/responsive-image-support-update\/","title":{"rendered":"Update: Responsive Image Support for Core"},"content":{"rendered":"

The responsive image team has been meeting regularly for a while. After our meeting earlier this week, we realized that make\/coreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> needs an update on what\u2019s been going on with the RICG (Responsive Images Community Group) feature pluginFeature Plugin<\/span> A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins<\/a><\/span><\/span><\/span>, as well as to request feedback on a few questions.<\/p>\n

Our meetings are in #feature-respimg<\/a> each Friday at 1900 UTC<\/abbr><\/a>, so please come and chat to give feedback or if you\u2019re interested in helping out!<\/p>\n

Background<\/h2>\n

Several years ago, a ragtag group of web professionals<\/a>\u00a0identified a need for\u00a0new HTMLHTML<\/span> HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.<\/span><\/span><\/span> markup\u00a0which would allow developers to\u00a0declare\u00a0multiple sources for an image\u2014allowing\u00a0devices to\u00a0select the image source that was most appropriate for its own capabilitiescapability<\/span> A\u00a0capability<\/strong>\u00a0is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can<\/code> function. Each user of a WordPress site might have some permissions but not others, depending on their\u00a0role. For example, users who have the Author role usually have permission to edit their own posts (the \u201cedit_posts\u201d capability), but not permission to edit other users\u2019 posts (the \u201cedit_others_posts\u201d capability).<\/span><\/span><\/span>. Fast forward to today and all major browsers have either implemented these new tools or currently have them under consideration for development.<\/p>\n

With that as background,\u00a0the RICG has been working on an Official WordPress Feature Plugin\u2122<\/em><\/a> to test the viability of adding responsive image support natively into WordPress. Specifically, our aim is to automatically add srcset<\/code>\u00a0(using w<\/code> descriptors) and sizes<\/code> attributes to the image markup generated by WordPress. According to the WordPress.org plugin directory<\/a>, there are over 10k active installs, so we\u2019ve definitely seen an interest in this functionality.<\/p>\n

There are two main pieces of functionality included in the pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span>, which can be considered separately for inclusion in core:<\/p>\n

    \n
  1. Logic for producing responsive image markup<\/li>\n
  2. Advanced image compression (via ImageMagick)<\/li>\n<\/ol>\n

    Responsive Image Markup<\/h2>\n

    There is a lot to consider when proposing a change to the way WordPress outputs image markup, so I want to be clear about some of our assumptions going in:<\/p>\n