feat: rework explore introduction

_data/navigation.yml

@@ -15,14 +15,10 @@ main:
 docs_explore:
   - title: First things first
     children:
-      - title: "Introduction"
-        url: /explore
+      - title: "How does Enmeshed work?"
+        url: /explore/how_does_enmeshed_work
       - title: "Example Scenarios"
         url: /explore/example-scenarios
-      - title: "Features"
-        url: /explore/features
-      - title: "Use Cases"
-        url: /explore/use-cases
       # - title: "Screens"
       #   url: /explore/screens
       - title: "Frequently Asked Questions"

_docs_explore/01-introduction.md → _docs_explore/01-how_does_enmeshed_work.md

@@ -1,41 +1,9 @@
 ---
-title: "Introduction"
-permalink: /explore
+title: "How does Enmeshed work?"
+permalink: /explore/how_does_enmeshed_work
 toc: true
 ---
 
-# What is Enmeshed?
-
-Enmeshed is an open source project combining various assets into an overarching digitalization approach for users and organizations. Its overall goal is to introduce a secure but easy-to-use way to share and request data and digital signatures between contacts.
-
-A focus is the digitalization of the end user: Enmeshed is bringing back control to the end user in an easy-to-use way and thus empowering its users to use the modern IT world which was usually an area only experts were able to cope with. With Enmeshed the user actively takes part of the business processes, allowing a whole new digital experience.
-
-On the other hand, many organizations are still having trouble to digitize their business processes. Enmeshed introduces a different mindset - as well as components and tools - on how to securely communicate with other organizations and users. All this is done while keeping an easy-to-integrate approach in mind.
-
-The adjective "enmeshed" (\in'meshd\ or \en'meshd\ or /ɪnˈmeʃt/ ) means "to be entangled in s.th." or "parts which are patched together". Though sometimes used with a negative touch, nowadays we are all enmeshed in digital processes somehow, with more or less user satisfactory and effectiveness.
-
-We think by not only connecting identities of users and organizations to those digital processes, but tightly interweaving them within the actual processes, the overall user experience and process efficiency will rise. Enmeshed identities have a secure, digital and modern link between each other, which is not only used for overall communication but for professional processes.
-
-For us, being enmeshed is a very good thing: you know what is going on and the data which is used. You can take part in completely digital processes, without the hazzle of repeating yourself again and again. Even automated actions are available for end users.
-
-Sounds promising? Learn more about why we are doing this in the next chapter.
-
-# Why Enmeshed?
-
-Digitalization is one of the big challenges in the 21st century.
-
-However, digitalization projects tend to be cumbersome, get out of time / budget, and get complicated very fast. The problem scope is so vast, that experts usually focus on specific topics and very few people have an overarching view on top of desirability, feasibility, and visibility.
-
-The common approach to tackle the digitalization is a siloed-one, many software vendors, consulting agencies and technologies try to focus on some of the technical problems, but usually not all of them.
-
-A digitalization of the "last mile" to the end user is usually not in scope of these approaches. This also includes the secure communication to the end user, which is often tackled by providing them with additional online accounts and multi factor authentication approaches to download specific information manually.
-
-So far there is no user-centric approach for digitalization: Each organization creates own solutions for digitizing their specific business processes which are usually not compatible to other digitalization solutions. In the end the user has to manually combine the various solutions to manage its own digital life. This is why a user nowadays has so many different accounts, contact details, old master data, and so on...
-
-You know what we mean? Have a look at the next chapter for a quick introduction on how Enmeshed works.
-
-# How does Enmeshed work?
-
 Enmeshed introduces an overarching solution, securely connecting users and organizations without the use of decentralized technologies like blockchains. However, it makes use of the decentralized mindset, like decentralized identities.
 
 Mature technologies and architectures are used as a base for Enmeshed. In combination with state-of-the-art encryption technologies, a complete web stack is used for all features, making Enmeshed a very powerful yet portable and modular stack for solving many challenges within various scenarios and industries.
@@ -85,9 +53,3 @@ The Backbone is based on a microservice architecture and is highly virtualized w
 The client for organizations is the [Enmeshed Connector]({% link _docs_explore/52-connector.md %}). It acts with a separate digital identity of the organization within the network of the organization. Thus, it is in the hands of the corresponding IT department and can be set up next to the organization's business systems using the majority of the features.
 
 The Connector is hosted by a single Docker container and provides a REST API for all features of the transport layer. It can thus be perfectly used for integration purposes. The Connector transparently encrypts or decrypts the respective payload, synchronizes with the Backbone and keeps track of the Enmeshed data.
-
-# Who is behind Enmeshed?
-
-The idea of Enmeshed is based on the work of many others in the area of open source software, encryption, decentralized identities, decentralized ledgers, and so on. These approaches were combined by a group of people who envisioned a great digital experience for everybody.
-
-So far, the primary implementation work has been done by j&s-soft GmbH in Heidelberg, Germany.

_docs_explore/02-explore.md

@@ -0,0 +1,26 @@
+---
+title: "Explore"
+permalink: /explore
+---
+
+Welcome to the "Explore Enmeshed" section of our website, your gateway to understanding the intricate world of Enmeshed. Here, we embark on a journey through the various facets of Enmeshed, from its fundamental workings to advanced technical insights.
+
+## First things first
+
+In this section, we lay the foundation by addressing the fundamental aspects of Enmeshed. We start by explaining how Enmeshed works, explore example scenarios, highlight its features and provide answers to commonly asked questions.
+
+## How we think
+
+Discover our perspective on Enmeshed as we delve into the mindset behind its development. We discuss integration considerations, security aspects and privacy considerations that shape our approach to creating a secure and privacy-conscious platform.
+
+## Our Layers
+
+Unveil the layers that make Enmeshed a robust and versatile solution. We'll guide you through each layer of the Enmeshed architecture, including the Backbone Layer, Transport Layer, Consumption Layer, Integration Layer and User-Experience Layer.
+
+## Components in-detail
+
+Get an in-depth look at the key components that power Enmeshed. Learn about the App, Backbone, and Connector and gain insights into how these elements contribute to the Enmeshed ecosystem.
+
+## Expert Corner
+
+For those seeking advanced knowledge, our Expert Corner is the place to be. Explore topics such as Enmeshed Addresses, Runtime behavior, Cryptography and the rationale behind our decision not to use blockchain technology.

_posts/2022-06-27-announcing-enmeshed-v2.md

@@ -20,7 +20,7 @@ For an overview of the changes regarding Attributes, please refer to the [corres
 
 Requests in Enmeshed always defined a way to exchange structured data. In Enmeshed V1 this was exclusively about Attributes. Requests in V2 will also be able to exchange data without persisting them to the User's Attributes, e.g. using a form.
 
-In Enmeshed V1 `RelationshipTemplates` and `RequestMails` each defined their own way for exchanging Attributes. Further only the App could process them. When integrating via the Connector you had to manually process all Requests. For V2 we pulled the Request handling [from the User-Experience Layer to the Consumption layer]({% link _docs_explore/01-introduction.md %}#layers). This enabled us to provide you with an API in the Connector to work with Requests. It also helped us making Request handling more flexible and easier to use.
+In Enmeshed V1 `RelationshipTemplates` and `RequestMails` each defined their own way for exchanging Attributes. Further only the App could process them. When integrating via the Connector you had to manually process all Requests. For V2 we pulled the Request handling [from the User-Experience Layer to the Consumption layer]({% link _docs_explore/01-how_does_enmeshed_work.md %}#layers). This enabled us to provide you with an API in the Connector to work with Requests. It also helped us making Request handling more flexible and easier to use.
 
 For an overview of Requests, please refer to the [corresponding blog post]({% post_url 2022-07-13-announcing-enmeshed-v2-requests %}).
 

_posts/2022-07-13-announcing-enmeshed-v2-requests.md

@@ -26,7 +26,7 @@ Requests in Enmeshed always defined a way to exchange structured data. In Enmesh
 
 Requests in V2 extend the Request featureset by providing more structured Requests, as well as Requests for unstructured data. Additionally, they are not fixed to the Identitity's Attributes. One example is a form you can send to a User, which contains some questions in natural language, which does not affect the Attributes. Another example is a Multi-Factor-Authentication Request which might be available in the future.
 
-In Enmeshed V1 `RelationshipTemplates` and `RequestMails` each defined their own way for exchanging Attributes. Further only the App could process them. When integrating via the Connector you had to manually process all Requests. For V2 we pulled the Request handling [from the User-Experience Layer to the Consumption layer]({% link _docs_explore/01-introduction.md %}#layers). This enabled us to provide you with an API in the Connector to work with Requests. It also helped us making Request handling more flexible and easier to use.
+In Enmeshed V1 `RelationshipTemplates` and `RequestMails` each defined their own way for exchanging Attributes. Further only the App could process them. When integrating via the Connector you had to manually process all Requests. For V2 we pulled the Request handling [from the User-Experience Layer to the Consumption layer]({% link _docs_explore/01-how_does_enmeshed_work.md %}#layers). This enabled us to provide you with an API in the Connector to work with Requests. It also helped us making Request handling more flexible and easier to use.
 
 ## Exchanging Requests
 

index.md

@@ -48,3 +48,39 @@ feature_ssi:
 {% include feature_row %}
 
 {% include feature_row id="feature_ssi" type="center" %}
+
+# What is Enmeshed?
+
+Enmeshed is an open source project combining various assets into an overarching digitalization approach for users and organizations. Its overall goal is to introduce a secure but easy-to-use way to share and request data and digital signatures between contacts.
+
+A focus is the digitalization of the end user: Enmeshed is bringing back control to the end user in an easy-to-use way and thus empowering its users to use the modern IT world which was usually an area only experts were able to cope with. With Enmeshed the user actively takes part of the business processes, allowing a whole new digital experience.
+
+On the other hand, many organizations are still having trouble to digitize their business processes. Enmeshed introduces a different mindset - as well as components and tools - on how to securely communicate with other organizations and users. All this is done while keeping an easy-to-integrate approach in mind.
+
+The adjective "enmeshed" (\in'meshd\ or \en'meshd\ or /ɪnˈmeʃt/ ) means "to be entangled in s.th." or "parts which are patched together". Though sometimes used with a negative touch, nowadays we are all enmeshed in digital processes somehow, with more or less user satisfactory and effectiveness.
+
+We think by not only connecting identities of users and organizations to those digital processes, but tightly interweaving them within the actual processes, the overall user experience and process efficiency will rise. Enmeshed identities have a secure, digital and modern link between each other, which is not only used for overall communication but for professional processes.
+
+For us, being enmeshed is a very good thing: you know what is going on and the data which is used. You can take part in completely digital processes, without the hazzle of repeating yourself again and again. Even automated actions are available for end users.
+
+Sounds promising? Learn more about why we are doing this in the next chapter.
+
+# Why Enmeshed?
+
+Digitalization is one of the big challenges in the 21st century.
+
+However, digitalization projects tend to be cumbersome, get out of time / budget, and get complicated very fast. The problem scope is so vast, that experts usually focus on specific topics and very few people have an overarching view on top of desirability, feasibility, and visibility.
+
+The common approach to tackle the digitalization is a siloed-one, many software vendors, consulting agencies and technologies try to focus on some of the technical problems, but usually not all of them.
+
+A digitalization of the "last mile" to the end user is usually not in scope of these approaches. This also includes the secure communication to the end user, which is often tackled by providing them with additional online accounts and multi factor authentication approaches to download specific information manually.
+
+So far there is no user-centric approach for digitalization: Each organization creates own solutions for digitizing their specific business processes which are usually not compatible to other digitalization solutions. In the end the user has to manually combine the various solutions to manage its own digital life. This is why a user nowadays has so many different accounts, contact details, old master data, and so on...
+
+You know what we mean? Have a look at the next chapter for a quick introduction on how Enmeshed works.
+
+# Who is behind Enmeshed?
+
+The idea of Enmeshed is based on the work of many others in the area of open source software, encryption, decentralized identities, decentralized ledgers, and so on. These approaches were combined by a group of people who envisioned a great digital experience for everybody.
+
+So far, the primary implementation work has been done by j&s-soft GmbH in Heidelberg, Germany.