docs: styling, concepts cleanup (#2643)

* Architecture Scenarios B2B B2C

* b2b b2c

* cleanup concepts

* homepage links, b2c docs

* b2c, new homepage, custom components

* more content

* fix rxjs

* temp remove architecture scenarios

* temp remove architecture scenarios

* Update docs/src/pages/index.js

Co-authored-by: Florian Forster <florian@caos.ch>

* update docusaurus & review scenarios

* refactor user login guide (#2921)

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2c.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2c.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: mffap <mpa@caos.ch>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: mffap <mpa@caos.ch>

* Update docs/docs/guides/architecture-scenarios/b2b.mdx

Co-authored-by: mffap <mpa@caos.ch>

* Update docs/docs/guides/architecture-scenarios/b2c.mdx

Co-authored-by: mffap <mpa@caos.ch>

* Update docs/docs/guides/architecture-scenarios/b2c.mdx

Co-authored-by: mffap <mpa@caos.ch>

* Update docs/docs/guides/architecture-scenarios/b2c.mdx

Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>

* user-login splitup

* files

* organize files

* cleanup authmethods

* solution scenarios

* add link to authz

* Update docs/docs/guides/authentication/authmethods/implicit.mdx

Co-authored-by: Livio Amstutz <livio.a@gmail.com>

* Update docs/docs/guides/authentication/authmethods/implicit.mdx

Co-authored-by: Livio Amstutz <livio.a@gmail.com>

* fix broken links

* Update docs/docs/guides/solution-scenarios/b2c.mdx

Co-authored-by: Florian Forster <florian@caos.ch>

* c for consumer

Co-authored-by: Florian Forster <florian@caos.ch>
Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com>
Co-authored-by: mffap <mpa@caos.ch>
Co-authored-by: Livio Amstutz <livio.a@gmail.com>

docs/docs/concepts/eventstore.md

@@ -2,7 +2,7 @@
 title: Eventstore
 ---
 
-ZITADEL is built on the [event sourcing pattern](../zitadel/architecture.md), where changes are stored as events in an eventstore.
+ZITADEL is built on the [event sourcing pattern](./architecture), where changes are stored as events in an eventstore.
 
 ## What is an eventstore?
 

docs/docs/concepts/introduction.md

@@ -1,7 +0,0 @@
----
-title: Introduction
----
-
-This part of the **ZITADEL** documentation contains ZITADEL specific or general concepts required to understand the system or our guides.
-
-Please be reminded that ZITADEL is open source — and so is the documentation. Should you happen to stumble over an incorrectness, a spelling mistake, a hard-to-understand text passage, please don’t hesitate to leave a comment or propose a corresponding change.

docs/docs/concepts/introduction.mdx

@@ -0,0 +1,39 @@
+---
+title: Introduction
+---
+
+import {ListElement, ListWrapper, ICONTYPE} from '../../src/components/list';
+import Column from '../../src/components/column';
+
+This part of the **ZITADEL** documentation contains ZITADEL specific or general concepts required to understand the system or our guides.
+
+Please be reminded that ZITADEL is open source — and so is the documentation. Should you happen to stumble over an incorrectness, a spelling mistake, a hard-to-understand text passage, please don’t hesitate to leave a comment or propose a corresponding change.
+
+
+<Column>
+  <ListWrapper title="General">
+    <ListElement link="./principles" type={ICONTYPE.TASKS} title="Principles" description="Design and engineering principles" />
+    <ListElement link="./eventstore" type={ICONTYPE.STORAGE} title="Eventstore" description="Learn how ZITADEL stores data" />
+    <ListElement link="./architecture" type={ICONTYPE.ARCHITECTURE} title="Architecture" description="Sotware-, Cluster- and Multi Cluster Architecture" />
+  </ListWrapper>
+  <ListWrapper title="Structure">
+    <Column>
+      <div>
+      <ListElement link="./structure/overview" type={ICONTYPE.FOLDER} title="Overview" description="" />
+      <ListElement link="./structure/organizations" type={ICONTYPE.FILE} title="Organizations" description="" />
+      <ListElement link="./structure/policies" type={ICONTYPE.FILE} title="Policies" description="" />
+      <ListElement link="./structure/projects" type={ICONTYPE.FILE} title="Projects" description="" />
+    </div>
+    <div>
+      <ListElement link="./structure/applications" type={ICONTYPE.FILE} title="Applications" description="" />
+      <ListElement link="./structure/granted_projects" type={ICONTYPE.FILE} title="Granted Projects" description="" />
+      <ListElement link="./structure/users" type={ICONTYPE.FILE} title="Users" description="" />
+      <ListElement link="./structure/managers" type={ICONTYPE.FILE} title="Managers" description="" />
+    </div>
+    </Column>
+  </ListWrapper>
+
+  <ListWrapper title="Use Cases">
+    <ListElement link="./usecases/saas" type={ICONTYPE.START} title="SaaS" description="Product with Authentication and Authorization" />
+  </ListWrapper>
+</Column>

docs/docs/concepts/structure/applications.md

@@ -18,4 +18,5 @@ As a fourth option there's the API (OAuth Resource Server), which generally has
 
 Depending on the app type registered, there are small differences in the possible settings.
 
-Please read the following guide about the [different-client-profiles](../../../guides/authorization/oauth-recommended-flows#different-client-profiles).
+Please read the following guide about the
+[different-client-profiles](../../guides/authorization/oauth-recommended-flows#different-client-profiles).

docs/docs/concepts/structure/overview.md

@@ -1,5 +1,5 @@
 ---
-title: Structure
+title: Overview
 ---
 
 This overview shows the general structure of ZITADEL.

docs/docs/concepts/structure/policies.md

@@ -55,7 +55,7 @@ You can configure all kinds of external identity providers for identity brokerin
 Create a new identity provider configuration and enable it in the list afterwards.
 
 For a detailed guide about how to configure a new identity provider for identity brokering have a look at our guide:
-[Identity Brokering](../../../guides/authentication/identity-brokering)
+[Identity Brokering](../../guides/authentication/identity-brokering)
 
 ## Lockout Policy
 

docs/docs/concepts/structure/projects.md

@@ -11,7 +11,7 @@ import ProjectDescription from './_project_description.mdx';
 ## Project Settings
 
 On default the login screen will be shown in the private labeling settings of the system (e.g zitadel.ch).
-With the [primary domain scope](../../../apis/openidoauth/scopes#reserves-scopes) it is possible to trigger the setting of the given organization. 
+With the [primary domain scope](../../apis/openidoauth/scopes#reserves-scopes) it is possible to trigger the setting of the given organization. 
 But this will also restrict, the login to user of the given organization.  
 
 With the private labeling setting it is possible to choose which settings should trigger.

docs/docs/concepts/usecases/saas.md

@@ -1,5 +1,5 @@
 ---
-title: Saas Product with Authentication and Authorization
+title: SaaS Product with Authentication and Authorization
 ---
 
 This is an example architecture for a typical SaaS product.