docs: update Guide menu

docs/.vitepress/config.mts

@@ -43,10 +43,9 @@ export default defineConfig({
       {
         text: "Guide",
         items: [
-          { text: "Organization admins", link: "/guides/Orgadmin/intro" },
           { text: "Wallet App", link: "/guides/Wallet/wallet" },
-          { text: "Verifier App", link: "/guides/Verifier/verifier" },
-		  { text: "Credential issuance", link: "guides/Orgadmin/issuance_flow" },	  
+		  { text: "Credential issuance", link: "guides/Flows/basics" },	 
+		  { text: "Microservices", link: "guides/Flows/microservices" },	 
           { text: "Signatures", link: "/guides/Signature/signatures" },
 		  { text: "Sysadmins", link: "/guides/Sysadmin/sysadmin" },
         ],

docs/guides/Flows/basics.md

@@ -23,6 +23,13 @@ The templates contain the core logic that govern the issuance and verification f
 
 - **Where are templates executed?**
   Depending if it's an *Authorization*, *Issuance* or *Verification*, the templates are executed inside a Microservice, inside the Wallet or inside the Verifier App [more about this later].
+
+See how the Template Editor looks like:   
+
+| Template Editor  |  
+|--|
+| <img src="../images/dashboard/template-editor-long.png" alt="template-editor" width="1000"/> |  
+
 
 
 ## Issuance and Verification Flows
@@ -39,6 +46,13 @@ Flows define the full behaviour of credential issuance and verification. While t
 
 Credential Issuance and Verification are (partly) executed in Microservices. The Microservices are configured in the Dashboard, the Dashboard also provides you with the actuall Microservices code, with different deployment possibilities.  
 
+See below the *Home > Organization > Microservices* page:
+
+
+| Microservices list and Deployment  |  
+|--|
+| <img src="../images/dashboard/microservices-manual-deployment-small.png" alt="microservices-manual-deployment-small" width="1000"/> |  
+
 
 ## Toolchain and components
 

docs/guides/Flows/templates.md

@@ -59,7 +59,7 @@ This contains the core logic of the Template. The Custom code can:
  - Create and process data on the fly
  - Return the processed data: some types of Template, have a certain return data format (e.g. Authorization Template must return a JSON object named "data") but each template can send the output to a REST API or write it into a Database. The parameters relevant to REST APIs and Parameters must be loaded from "Zencode data" (see Presets for examples). 
 
-| Templates Editor  |  
+| Template Editor  |  
 |--|
 | <img src="../images/dashboard/template-editor-long.png" alt="template-editor" width="1000"/> |