| 3 | | - given the general confusion on how to add a static file to a |
| 4 | | project, I would rewrite the first part so that it goes straight |
| 5 | | to the point: ie. "Install a static file in your project: |
| 6 | | how to add jQuery" |
| 7 | | - second part of the tutorial would be deployment, |
| 8 | | - third part would be using app/static subfolder, |
| 9 | | - wording issues, for example "assets" is a word I (as a self |
| 10 | | learner, non english) learnt from reading about Rails, so I |
| 11 | | think it can be confusing for other users. It would be better to |
| 12 | | name "static files" just "static files" |
| 13 | | |
| 14 | | Also, I have tried django 1.5 starter project: it looks like every django project that will need at least one static file (most projects) will have to setup `STATICFILES_DIRS=[os.path.join(BASE_DIR, 'static')]`. What's the point ? Couldn't we change that and make it default ? |
| 15 | | |
| 16 | | I mean, it could potentially be as easy as: |
| 17 | | |
| 18 | | > drop style.css in `your_project/static` and use |
| 19 | | > `{{ STATIC_URL }}style.css` or `{% static 'style.css' %}` in the template |
| 20 | | |
| 21 | | (Sorry I had totally forgotten about this and forgot to CC myself |
| 22 | | ... Note that I've read both document and I can ensure |
| 23 | | that every point listed by Zed has a response in the new |
| 24 | | tutorial.) |
| | 3 | I think it is more straight forward, and it should match expectations of newcomers which Zed so elegantly described :) |