## Summary - Add comprehensive Ukrainian language support to ZITADEL - Complete translation of all user-facing interfaces - Integration with existing language configuration system ## Changes Made - ✅ **Console translations**: Complete Ukrainian translation for admin console (2,861 translated strings) - ✅ **Login interface**: Ukrainian translations for authentication flows (535 strings) - ✅ **Email notifications**: Ukrainian translations for system emails (68 strings) - ✅ **Common texts**: Ukrainian translations for success/error messages (1,417 strings) - ✅ **Language configuration**: Added Ukrainian to supported languages and Angular locale registration - ✅ **UI integration**: Added Ukrainian option to language selection forms ## Translation Quality - Professional translations using established Ukrainian IT terminology - Formal language appropriate for business software - Consistent terminology across all components (Users→Користувачі, Organization→Організація, etc.) - Preserved all technical placeholders, HTML tags, and formatting ## Contributing Guidelines Compliance - ✅ Followed semantic commit message format - ✅ Added Ukrainian to all required configuration files - ✅ Maintained consistent file structure with existing languages - ✅ Used formal Ukrainian appropriate for business software The Ukrainian translation is now ready for review by the ZITADEL team! 🚀 --------- Co-authored-by: Marco A. <[email protected]>
Zitadel Console
The Console is Zitadels management UI.
It is built using Angular and part of the Zitadel monorepo.
To get started follow the contributing quick start.
Building
To build for production:
pnpm nx run @zitadel/console:build
This will:
- Generate proto files (via
prebuildscript) - Build the Angular app with production optimizations
Linting
To run linting and formatting checks:
pnpm nx @zitadel/console:lint
To auto-fix formatting issues:
pnpm nx @zitadel/console:lint-fix
Project Structure
src/app/proto/generated/- Generated proto files (Angular-specific format)buf.gen.yaml- Local proto generation configurationproject.json- Nx orchestration and caching for builds and testsprebuild.development.js- Development environment configuration script
Dependency Chain
The Console app has the following build dependencies managed by Nx:
@zitadel/proto:generate- Generates the protobuf stubs@zitadel/client:build- Builds the TypeScript gRPC client library@zitadel/console:generate- Generates Console-specific protobuf stubs@zitadel/console:build- Creates a production build from Console
This ensures that the Console always has access to the latest client library and protobuf definitions.
Proto Generation Details
@zitadel/protogeneration: Modern ES modules with@bufbuild/protobuffor v2 APIs- Local
buf.gen.yamlgeneration: Traditional protobuf JavaScript classes for v1 APIs
The Console app calls Zitadel v1 and v2 APIs. As long as the Console still calls v1 APIs, it needs to import client stubs from separate sources:
Legacy v1 API (Traditional Protobuf)
- Uses local
buf.gen.yamlconfiguration - Generates traditional Google protobuf JavaScript classes extending
jspb.Message - Uses plugins:
protocolbuffers/js,grpc/web,grpc-ecosystem/openapiv2 - Output:
src/app/proto/generated/ - Used for: Most existing Console functionality
Modern v2 API (ES Modules)
- Uses
@zitadel/protopackage generation - Generates modern ES modules with
@bufbuild/protobuf - Uses plugin:
@bufbuild/eswith ES modules and JSON types - Output:
login/packages/zitadel-proto/ - Used for: New user v2 API and services
Dependency Management
The Console's project.json ensures proper execution order:
@zitadel/proto:generateruns first (modern ES modules)- Console's local generation runs second (traditional protobuf)
- Build/lint/start tasks depend on both generations being complete
This approach allows the Console app to use both v1 and v2 APIs while maintaining proper build dependencies.
Legacy Information
This project was originally generated with Angular CLI version 8.3.20 and has been updated over time.