Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Provide a 'Use Cases for Authors' document (or similar introductory content). #27

paulrobertlloyd opened this Issue Dec 16, 2012 · 4 comments


None yet
4 participants

The use cases document (http://usecases.responsiveimages.org) is written using a style and tone aimed at browser vendors and others with deep knowledge of the subject.

While this document is useful for that audience, there is a second audience of designers and developers who would be better served by having more approachable content available to them.

A page or section on the responsiveimages.org site should explain the use cases in plain English. This could point to (further) examples where these use cases exist already in the wild, noting perhaps how such implementations result in users having to download unnecessary data than is required (for example).

If people wishing to get involved with RICG need to understand the use cases (why they matter, where they've arisen from, how they can't be addressed using current markup etc.), it is important that this information is available in an easy to understand and accessible format.


marcoscaceres commented Dec 16, 2012

@paulrobertlloyd, could not agree more. I'm sorry to hear the language we are using is coming across as overly targeted at browser folks:( The primary audience for all our documents was intended to be web developers. Could use your help making sure we articulate things more clearly? I personally think all the things you mention above should be in the use cases doc. Remember it's a living document so we are happy to change it to make it better! Pull request or just pointers to where language is problematic are welcome.

@ghost ghost assigned Wilto Dec 19, 2012


marcoscaceres commented Dec 28, 2012

@paulrobertlloyd we are planning to publish in about 2 weeks, so please let us know what you would like to see changed.


Wilto commented Dec 28, 2012

Yeah; I want to have this and the updates FAQ ready for publication. I’m happy to take point, and it’ll be open for feedback/collaboration well before.


anselmh commented Mar 2, 2014

Can we close this as it’s basically being covered in / a duplicate of #28?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment