mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
59f1105b04
# Which Problems Are Solved For username/email + password, "login data" seems like uncommon and confusing terminology to me. I also think "loginname" is that, maybe it should be written like "login name" or "username", but I'm having oversight with that now because it seems to be the way Zitadel calls it. Here's what Gemini has to say: > Login Credentials: This is the most widely accepted and formal term in the tech and security industry. A "credential" is an item of information that confirms an identity. The pair (username/email and password) is the set of identifiers used to authenticate the user and grant access (i.e., log in). > > Login Details: This is also very common in general use and often used interchangeably with "login credentials," especially in user-facing contexts (e.g., "Please enter your login details"). It is slightly less formal than "credentials." > > Login Data: While technically correct (as the information is data), this term is less specific and is more commonly used when referring to a larger collection of information, like a file containing many users' credentials, or the data transmitted during the login process. # How the Problems Are Solved Renames all occurrences of login data or login credentials to login details. # Additional Changes None. # Additional Context I believe this is an improvement but feel free to object. Co-authored-by: Max Peintner <[email protected]> Co-authored-by: Ramon <[email protected]>
@zitadel/docs
Documentation for Zitadel, built with Fumadocs and Next.js.
Getting Started
Ensure you have followed the root quick start to set up dependencies.
Local Development
Start the development server:
pnpm nx run @zitadel/docs:dev
The site will be available at http://localhost:3000.
Scripts
Key scripts for documentation workflows:
| Script | Description |
|---|---|
dev |
Starts the development server. |
build |
Builds the production application. |
fetch:remote-content |
Fetches remote tags and referenced content. |
generate |
Runs all generation steps (fetch:remote-content, generate:proto-docs, generate:api-reference, generate:index-pages). |
check:links |
Validates content integrity (broken links, missing frontmatter, schema errors). |
check-types |
Validates typescript types. |
test |
Runs all validation steps (check-types, check:links). |
lint |
checks for code style and syntax errors (ESLint). |
clean |
Cleans the build output and generated files. |
Validation
- Code Quality: Run
pnpm lintto check for syntax and style issues in JS/TS/MDX files. - Content Integrity: Run
pnpm check:linksto validate content structure, including:- Broken internal links
- Missing required front-matter (e.g.,
title) - Image references
Contributing
Build Process
The docs build process automatically handling the following steps via generate:
- Downloads required protoc plugins.
- Generates gRPC documentation from proto files.
- Generates API documentation from OpenAPI specs.
- Generates index files for directory structures.
Style Guide
- Variables: Use environment variables in code snippets where possible.
- Embedded Content: Use
_filename.mdxfor content embedded in other pages (not indexed individually). - Code Embedding: Use the
fileproperty in code blocks to embed code from the repo. - Voice: Use active voice and sentence case for titles.
Refer to the Google Developer Style Guide for general guidelines.
Adding Content
All documentation content is located in the content directory. Note that the system strictly accepts only .mdx files.
To add a new page:
- Create a
.mdxfile in the appropriate subdirectory ofcontent. - Register the new page in the sidebar configuration at
lib/sidebar-data.tsto make it accessible in the navigation.
Pull Requests
Use docs(<scope>): <short summary> for PR titles.
Pass quality checks before submitting:
pnpm nx run @zitadel/docs:build
pnpm nx run @zitadel/docs:check:links
You can also run specific steps individually:
pnpm fetch:remote-contentpnpm generate:api-reference