+ Honestly it's not yet very clear sometimes what 'where-it-belongs' should be sometimes, and it
+ does not matter too much anyway, given that the code doesn't need to change when we move things
+ around. So in particular it's fuzzy between myslice/ (where the logo could fit e.g.) views/ and
+ even trash/
+
+Makefile has a few convenience targets to list all kinds of stuff; the 2 major targets are
+
+$ make static templates
+
+that would reset all-static/ and all-templates/ for you from the other contents
+
+* third-party
+ please note that the set of files that actually get exposed in all-static from third-party is
+ hand-coded in Makefile because we tried to preserve the original codebase layout from mainstream,
+ and there's only so much in common between 2 differents js libraries at this point.
+
+
+
+======== update django database to reflect changes in existing models without any migration system (e.g., south) =========
+
+# older version
+$python manage.py reset <your_app>
+
+#Django 1.5.1 or later
+$python manage.py flush
+
+This will update the database tables for your app, but will completely destroy any data that existed in those tables.
+If the changes you made to your app model do not break your old schema (for instance, you added a new, optional field)
+you can simply dump the data before and reload it afterwards, like so:
+
+$python manage.py syncdb
+$python manage.py dumpdata <your_app> > temp_data.json
+$python manage.py flush
+$python manage.py loaddata temp_data.json
+
+If your changes break your old schema this won't work - in which case tools like south or django evolution are great.
+
+======== update django database to reflect changes in existing models with migration system (e.g., south) =========
+
+As south is already installed , you just have to do:
+
+$./manage.py migrate
+
+if it fails:
+
+1. go to myslice directory
+2. do sqlite3 myslice.sqlite3 [if sqlite3: command not found, do $apt-get install sqlite3]
+3. check the list of tables with sqlite> .tables
+4. if you find those tables that was mentioned in the failure message while running $./manage.py migrate
+ do sqlite> DROP TABLE mentioned_table
+ [mentioned_table = the tables that was explicity mentioned in the failure message of $./manage.py migrate]
+5. sqlite> .quit
+6. $./manage.py migrate
+