Fixes #3 - Share app store buttons

Fixes #3 - Share app store buttons

[ire, 2018-05-28 11:17:12]

Ready for review!

Notes:

1. There is no SVG version of the Google Play Badge (only alternative to png is
EPS, and because of DRM protection we can't convert it)
2. I'm starting to think we should namespace things from website-defaults. So
instead of just `locales/en/img` it would be `locales/en/wd/img` so when we use
the image it'll be "wd/img/png/google-play-badge.png", what do you think? (I
think you suggested something like this before)

[juliandoucette, 2018-05-29 12:03:41]

On 2018/05/28 11:17:12, ire wrote:

LGTM

> 2. I'm starting to think we should namespace things from website-defaults. So
> instead of just `locales/en/img` it would be `locales/en/wd/img` so when we
use
> the image it'll be "wd/img/png/google-play-badge.png", what do you think? (I
> think you suggested something like this before)

I

[juliandoucette, 2018-05-29 12:06:55]

On 2018/05/29 12:03:41, juliandoucette wrote:
> 2. I'm starting to think we should namespace things from website-defaults. So
> instead of just `locales/en/img` it would be `locales/en/wd/img` so when we
use
> the image it'll be "wd/img/png/google-play-badge.png", what do you think? (I
> think you suggested something like this before)

(I submitted prematurely by mistake.)

I'd prefer not to namespace resources inside the website-defaults repository.
Instead, we may namespace a dependency in a website's settings.ini. I forget
whether or not we have implemented this namespacing feature inside the CMS yet.

Anyway, I think this implementation is good for now.

[ire, 2018-05-29 15:50:39]

On 2018/05/29 12:06:55, juliandoucette wrote:
> On 2018/05/29 12:03:41, juliandoucette wrote:
> > 2. I'm starting to think we should namespace things from website-defaults.
So
> > instead of just `locales/en/img` it would be `locales/en/wd/img` so when we
> use
> > the image it'll be "wd/img/png/google-play-badge.png", what do you think? (I
> > think you suggested something like this before)
> 
> (I submitted prematurely by mistake.)
> 
> I'd prefer not to namespace resources inside the website-defaults repository.
> Instead, we may namespace a dependency in a website's settings.ini. I forget
> whether or not we have implemented this namespacing feature inside the CMS
yet.
> 
> Anyway, I think this implementation is good for now.

Ack. Namespacing via the settings.ini would be preferable anyway. Thanks!