[RFC] Provide core implement or enhanced documentation for high-traffic issues

[robfrawley]

Q	A
Bug Report?	no
Feature Request?	yes
BC Break Report?	no
RFC?	yes
Imagine Bundle Version	n/a

I was glancing through the graph pages for this repo and stumbled upon the "popular content" section of GitHub's traffic graphs when an idea struck me.

The "popular content" listing gives us an idea of what issues are visited most and provides us insight into where we should focus our efforts to directly help consumers of this bundle, either through core feature or enhancement implementations, or better documentation through collation of issue comments.

Here are the top items:

• #852: "Question - Avoid caching the default "not found" image"
• #194: "Thumbnails doesn't appear and are not created"
• #849: "Multiple "Source image could not be found" since 1.7 update"
• #328: "Does LiipImagineBundle support remote image?"
• #203: "Complete S3 Setup: Original Images and cached Images on AWS S3"

[alexwilson]

Very nice find, and I completely agree that we should focus on offering up better documentation for these sorts of issues (especially if it helps people adopt this, and cuts down on issues). Perhaps something along the lines of a FAQ, or maybe we should look at changing the format of pre-existing documentation?

[robfrawley]

I also think we should provide a more plug-and-play, core implementation for AWS S3. There is too much boilerplate code needed for one to get up and running with it at the moment, IMHO.