geoadmin/mf-geoadmin3 — pull request #19 by elemoine (2013-06-24 12:13:06+00:00)
Title: More structure

One we have decided on make vs zc.buildout (#18) I'd suggest that we bring more structure to the repository. This is somewhat the mess right now. We place generated files at different locations, we mix web resources with build-related resources, etc.

I'd suggest that the root directory include build-related and package-related files and directories (Makefile or buildout.cfg, package.json, etc.) and doesn't include any web resources (HTML, JS, CSS).

So the web resources go in specific directories. I can see one directory for the actual sources and dev (`app`), and one for the built files (`app-build`). For production we can just create an Apache alias that points to the `app-build` directory.

See the proposed structures for `app` and `app-build` below. I haven't put that in place yet, but this is the direction I would suggest. This is obviously open to discussions.

```
app/
app/index.mako
app/index.html (generated from index.mako)
app/css
app/css/app.less
app/css/app.css (generated from app.less)
app/js/GaModule.js
app/js/map/
app/js/map/MapDirective.js
app/js/...
app/lib/ol.js
app/lib/ol-whitespace.js
app/lib/angular-1.1.5.js
app/lib/angular-1.1.5.min.js
app/lib/...
```

```
app-build/index.html (generated from index.mako)
app-build/css/app.min.css
app-build/js/app.min.js
app-build/lib (basically a copy of app/lib)
app-build/lib/ol.js
app-build/lib/ol-whitespace.js
app-build/lib/angular-1.1.5.js
app-build/lib/angular-1.1.5.min.js
app-build/lib/...
```