New version of images

Layout.md

@@ -24,9 +24,14 @@ As part of the communication coordination meetings in LEDGER project producing a
 
 ## 2. Structure of the materials and creation workflow
 
+Production of communication materials and the act of communicate follows this first diagram.
+Internally there are two main repository for shared materials: files, images, tempates, modules, temporary sharing, project folders etc. go on cloud.dyne.org, code and documentation and collectively written complex documents go on gitea.dyne.org.
+
 ![Workflow-simple.png](./images/Workflow-simple.png)
 
-Folder structure is to be kept in git or in nextcloud to availability of the consortium. Structure is the following. Workflow and notes will be put in readme.md in the appropriate folder.
+Folder structure for the communication cross partners and with participants is to be kept in git or in nextcloud to availability of the consortium and the perticipants. Structure is the one summarised in the following tree. Workflow and usage notes will be put in readme.md as it is custom with documentation.
+
+Follows the proposed taxonomy as a structure of folders
 
 ```
 
@@ -62,19 +67,20 @@ Communication
 
 ```
 ## 3. Materials (/Communication)
-General communication
+General communication groups are represented in this diagram. Access is readable by contact.
 
-![Internalcommunications.png](./images/Internalcommunications.png)
+![Internalcommunications.png](./images/InternalCommunication.png)
 
 
 
 ### 3.1. Brand (/Communication/1.Brand)
-LEDGER project has to be integrated into NGI brand guidelines and has to be divulgated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
+LEDGER project has to be integrated into NGI brand guidelines and has to be divagated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
 
 ####	3.1.1. brand book for LEDGER project
 A Brand book is a very good tool for general communication. It can evolve from the coordinate communication already studied for Ledger Project.
 It includes though some simplified answers to generic questions that allow to present the project properly to any of the people involved.
 It includes as well a general visual guideline.
+The book is a living doc that includes synonyms and explanations for key concepts.
 
 #####  Examples of Questions and Answers:
  - Q: What is LEDGER
@@ -90,7 +96,7 @@ It includes as well a general visual guideline.
 
 ### 3.3. Texts (/Communication/3.Texts)
 
-Some Examples of the textual material that will be compiled for the many editing purpoises necessary to the consortium communication.
+Some Examples of the textual material that will be compiled for the many editing purposes necessary to the consortium communication.
 
 ####	3.3.1. Internal-EU language register
 ##### Basic information and main goals of the LEDGER project
@@ -210,6 +216,12 @@ We are available to procure a professional WEB TV studio and a crew to assemble
 
 ### 3.8. Gadgets (/Communication/7.Gadgets)
 
+- T-Shirts
+- Hoodies
+- Stickers
+
+all we might come up with; the design will be kept here.
+
 ### 3.9. Other (/Communication/8.Others)
 
 ### 3.10. Projects-firstround (/Communication/9.projects-firstround)
@@ -303,4 +315,3 @@ system of retweet and how it has to work
 Other social Network Hashtag policies
 
 ## 8. Metrics
-