assets paths can be confusing

[joelanman]

could be part of the refactoring work.

The users assets live in /assets in the kit, and are processed then copied to /public.

Some other assets are mapped to /assets in server.js, this is confusing.

[36degrees]

@joelanman is this covered by #616?

[joelanman]

partly yes, I think it would also be good to look into having less confusing paths. 'assets' in the back end being different to 'assets' in the front end is a bit confusing

[joelanman]

I think this will be fixed by #613, which uses the path extension-assets