mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-08 21:52:10 +00:00
docs:change titles (#6582)
* Modified quick start guide to reflect the new onboarding changes. * Modified titles to optimize indexing. Left thet titles in title case for now. * Added side bar labels and also made minor changes to titles. * Update docs/docs/apis/openidoauth/endpoints.mdx Co-authored-by: Fabi <fabienne@zitadel.com> --------- Co-authored-by: Fabi <fabienne@zitadel.com>
This commit is contained in:
Dakshitha Ratnayake
committed by
GitHub
GitHub
parent
a5decda201
commit
599a1ddd78
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Secrets
|
||||
title: How ZITADEL Processes and Stores Secrets
|
||||
sidebar_label: Secrets
|
||||
---
|
||||
|
||||
In this chapter you can find information of how ZITADEL processes and stores secrets and credentials in a secure fashion.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Software
|
||||
title: ZITADEL's Software Architecture
|
||||
sidebar_label: Software Architecture
|
||||
---
|
||||
|
||||
ZITADEL is built with two essential patterns. Event Sourcing (ES) and Command and Query Responsibility Segregation (CQRS).
|
||||
@@ -14,7 +15,7 @@ Each ZITADEL binary contains all components necessary to serve traffic
|
||||
From serving the API, rendering GUI's, background processing of events and task.
|
||||
This All in One (AiO) approach makes operating ZITADEL simple.
|
||||
|
||||
## Software Structure
|
||||
## The Architecture
|
||||
|
||||
ZITADELs software architecture is built around multiple components at different levels.
|
||||
This chapter should give you an idea of the components as well as the different layers.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Deployment
|
||||
title: ZITADEL's Deployment Architecture
|
||||
sidebar_label: Deployment Architecture
|
||||
---
|
||||
|
||||
## High Availability
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Implementation
|
||||
title: ZITADEL Database Structure
|
||||
sidebar_label: Database Structure
|
||||
---
|
||||
|
||||
This documentation gives you an insight into the structure of the ZITADEL database.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Eventstore
|
||||
title: ZITADEL Event Store
|
||||
sidebar_label: Overview
|
||||
---
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Actions
|
||||
title: ZITADEL Actions
|
||||
sidebar_label: Actions
|
||||
---
|
||||
|
||||
By using ZITADEL actions, you can manipulate ZITADELs behavior on specific Events.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Audit Trail
|
||||
title: ZITADEL's In-built Audit Trail
|
||||
sidebar_label: Audit Trail
|
||||
---
|
||||
|
||||
ZITADEL provides you with an built-in audit trail to track all changes and events over an unlimited period of time.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Identity Brokering
|
||||
title: Identity Brokering in ZITADEL
|
||||
sidebar_label: Identity Brokering
|
||||
---
|
||||
|
||||
## What are Identity Brokering and Federated Identities?
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Self-Service
|
||||
title: Self Service in ZITADEL
|
||||
sidebar_label: Self Service
|
||||
---
|
||||
|
||||
ZITADEL allows users to perform many tasks themselves.
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Applications
|
||||
title: ZITADEL Applications
|
||||
sidebar_label: Applications
|
||||
---
|
||||
|
||||
# Applications
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Granted Projects
|
||||
title: ZITADEL's Granted Projects
|
||||
sidebar_label: Granted Projects
|
||||
---
|
||||
|
||||
# Granted Project
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Instance
|
||||
title: ZITADEL Instances
|
||||
sidebar_label: Instances
|
||||
---
|
||||
|
||||
## Instance Structure
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Managers
|
||||
title: ZITADEL Managers
|
||||
sidebar_label: Managers
|
||||
---
|
||||
|
||||
import ManagerDescription from "./_manager_description.mdx";
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Organizations
|
||||
title: ZITADEL Organizations
|
||||
sidebar_label: Organizations
|
||||
---
|
||||
|
||||
import OrgDescription from './_org_description.mdx';
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
---
|
||||
title: Settings/Policies
|
||||
title: ZITADEL Settings and Policies
|
||||
sidebar_label: Setting and Policies
|
||||
---
|
||||
|
||||
Settings and policies are configurations of all the different parts of the Instance or an organization. For all parts we have a suitable default in the Instance.
|
||||
Settings and policies are configurations of all the different parts of the instance or an organization. For all parts we have a suitable default in the instance.
|
||||
The default configuration can be overridden for each organization, some policies are currently only available on the instance level. Learn more about our different policies [here](/guides/manage/console/instance-settings.mdx).
|
||||
|
||||
API wise, settings are often called policies. You can read the proto and swagger definitions [here](../../apis/introduction.mdx).
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Projects
|
||||
title: ZITADEL Projects
|
||||
sidebar_label: Projects
|
||||
---
|
||||
|
||||
# Project
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Users
|
||||
title: ZITADEL Users
|
||||
sidebar_label: Users
|
||||
---
|
||||
|
||||
## Types of users
|
||||
|
||||
Reference in New Issue
Block a user