[wp-trac] [WordPress Trac] #21805: Retina, localized about screen screenshots

[WordPress Trac]

#21805: Retina, localized about screen screenshots
----------------------------+-----------------------
 Reporter:  nacin           |       Owner:  Otto42
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  3.5
Component:  Help/About      |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+-----------------------

Comment (by Otto42):

 List of current images in the download (from wp-admin/images/screenshots):

 {{{
 captions-1.png
 captions-2.png
 flex-header-1.png
 flex-header-2.png
 flex-header-3.png
 flex-header-media-library.png
 theme-customizer.png
 twitter-embed-1.png
 twitter-embed-2.png
 }}}

 Two options:

 1. Make an API endpoint (api/core/screenshots or api/core/about) to serve
 up array of screenshot URLs based on passed along localization params. API
 data could be maintained easily by simply having a static set of file
 listings on the API server, or have it dynamically built. Either works
 fine.
 2. Use rewriting to serve them statically based on filename (hit to
 wp.org/images/captions-1.png or wp.org/images/es-ES/captions-1.png,
 rewrites go to s.wp for the serving of the files) and so on. Rewrite rules
 would have to be maintained.

 Method 1 is more flexible but requires an extra API request to get the
 URLs. But it means we can build in backward compatibility easily by
 versioning the API request.

 Method 2 is faster and lower on resources, but requires maintenance of the
 rewrite rules (something that is currently inaccessible to me), and harder
 to maintain over time. Versioning would need to be in the URL as well,
 fallback to non-supported localizations, etc.

 I'm leaning toward method 1. Objections?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21805#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software