Google released the great [Web Starter Kit](https://developers.google.com/web/starter-kit/) a while ago and I was just wondering if anyone has used it in combination with AppEngine and/or Jinja2? I am not quite sure what the best practise is for using Web Starter Kit in AppEngine. 

I guess one possibility would be to develop the base layout template and stylesheets according the [Web Starter Kit build process](https://developers.google.com/web/fundamentals/tools/build/build_process#whats-in-the-web-starter-kit-build-process). Once the base layout has been finished, html and css files could be copied into the AppEngine project into the appropriate (static) folders. From there one could work on individual Jinja2 templates that extend the base template. The only pain is that changes to both CSS, images and the base template would always have to be copied over into their Jinja2/AppEngine directories.

Does anyone have a better idea in working with AppEngine, Jinja2 and the Web Starter Kit in a efficient way?

---

A few minutes and experiments later I created a `html_frontend` folder within the root directory. In that folder I am storing both `app` (contains the original html files) and `dist` (contains minimalised files). While I am developing in within `app`, I link static files and templates to the `app` directory. Also in my versioning control I am only checking in `app` as it contains the original files that can be used to compute the entire file and folder structure within `dist`. I am not sure yet though how to prevent AppEngine from uploading/deploying both `app` and `dist`.

---

The `app.yaml` would then look as follows:

```
- url: /styles
  static_dir: html_frontend/dist/styles
- url: /fonts
  static_dir: html_frontend/dist/fonts

```

---

This is how I eventually made it work: <https://stackoverflow.com/a/24892700/3628578>