static_content directory structure

[xavierba]

Hi,

The static_content directory structure is currently as follow (modified for readability):
.
├── external
│   ├── font-awesome
│   │   ├── css
│   │   └── fonts
│   ├── foundation
│   │   ├── css
│   │   └── js
│   ├── html5shiv
│   ├── images (this is the jquery-ui smoothness theme)
│   ├── jqplot.js
│   ├── jquery.js
│   ├── jquery-migrate.js
│   ├── jquery-ui.js
│   ├── modernizr.custom.js
│   └── respondjs
├── fonts
│   ├── foundation-icons
│   └── Raleway
├── icons
└── js
  └── sympa.js

The external directory name probably comes from the fact it's all bundled code.
The foundation-icons and raleway fonts are thus mislocated and should be moved into external.
That would left only icons (which origin is unsure) and sympa.js outside of external and thus makes me wonder if moving the fonts inside external is the right thing to do.
(On a side note sympa.js is clearly sympa code, but is missing a copyright header.)

Another directory structure could then be something like this:
.
├── fonts
│   ├── font-awesome
│   ├── foundation-icons
│   └── Raleway
├── icons
└── js
├── foundation
├── html5shiv
├── jqplot
├── jquery
├── jquery-migrate
├── jquery-ui
├── modernizr
├── respondjs
└── sympa

As @ikedas is working on upgrading to foundation6 (#170 ) and other related JS work, it might be a good time to discuss this.

On an unrelated note, distros are usually not fond of bundled code and usually unbundle it when possible. I'd like to discuss a mechanism to allow for simplify this unbundling work, maybe by allowing to specify the path for the system-provided javascripts and fonts at configure time and only install bundled code if not specified (which would be the default case indeed).
This is probably better discussed in a separate issue, but might influence the way to resolve this issue.

Regards,
Xavier