diff --git a/.DS_Store b/.DS_Store
index 96a0e00..aeea048 100644
Binary files a/.DS_Store and b/.DS_Store differ
diff --git a/projects/.DS_Store b/projects/.DS_Store
index 9a3c686..8609cbc 100644
Binary files a/projects/.DS_Store and b/projects/.DS_Store differ
diff --git a/projects/soup2/documentation.md b/projects/soup2/documentation.md
index 006e88d..b1b14a5 100644
--- a/projects/soup2/documentation.md
+++ b/projects/soup2/documentation.md
@@ -59,3 +59,10 @@ This could be interesting but maybe lead to obnoxious repetition of contents for
 Projects could have two different modes: one for annotate the process and one to publish the outcome. If im writing a log of development such as the [OOC @summer session](../ooc-summer-session/) page is something totally different from [SI17 Visual Identity](../postit-identity/), that is a final outcome.
 
 This could be made with a tag system for example, stating what page is a WIP and what is an outcome, but a different and more interesting approach could be something like the [text intensity of the textoscope](../textoscope/). Here something could be tagged directly while writing, with the possibility for the reader to modulate different levels of detail and polishing.
+
+### new identity
+
+Some sketches for a new visual identity i've done before summer, but im not sure I still like them ew. There is also a prototype for the auto-draw thumbnail preview. The real question is: are there energies to finish it or will it just remain a proof of concept? (the latter prob)
+
+![identity blu](identity.jpg)
+![identity blu](identity2.jpg)
diff --git a/projects/soup2/identity.jpg b/projects/soup2/identity.jpg
new file mode 100644
index 0000000..88cbdf5
Binary files /dev/null and b/projects/soup2/identity.jpg differ
diff --git a/projects/soup2/identity2.jpg b/projects/soup2/identity2.jpg
new file mode 100644
index 0000000..ea76e54
Binary files /dev/null and b/projects/soup2/identity2.jpg differ