translated localized doc copies

This commit is contained in:
AlexisLeDain
2026-04-08 21:11:09 +02:00
parent ddd611152e
commit 7945c3c979
12 changed files with 24 additions and 0 deletions

View File

@@ -4,6 +4,8 @@ description: Quarkus 3.x LTS architecture patterns with Camel for messaging, RES
origin: ECC
---
> **Note / 注意**: このファイルはまだ日本語に翻訳されていません。現在は英語の原文です。翻訳PRを歓迎します。
# Quarkus Development Patterns
Quarkus 3.x architecture and API patterns for cloud-native, event-driven services with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: Quarkus Security best practices for authentication, authorization,
origin: ECC
---
> **Note / 注意**: このファイルはまだ日本語に翻訳されていません。現在は英語の原文です。翻訳PRを歓迎します。
# Quarkus Security Review
Best practices for securing Quarkus applications with authentication, authorization, and input validation.

View File

@@ -4,6 +4,8 @@ description: Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito,
origin: ECC
---
> **Note / 注意**: このファイルはまだ日本語に翻訳されていません。現在は英語の原文です。翻訳PRを歓迎します。
# Quarkus TDD Workflow
TDD guidance for Quarkus 3.x services with 80%+ coverage (unit + integration). Optimized for event-driven architectures with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: "Verification loop for Quarkus projects: build, static analysis, te
origin: ECC
---
> **Note / 注意**: このファイルはまだ日本語に翻訳されていません。現在は英語の原文です。翻訳PRを歓迎します。
# Quarkus Verification Loop
Run before PRs, after major changes, and pre-deploy.

View File

@@ -4,6 +4,8 @@ description: Quarkus 3.x LTS architecture patterns with Camel for messaging, RES
origin: ECC
---
> **Not / Note**: Bu dosya henuz Turkceye cevrilmemistir, su anda Ingilizce orijinaldir. Ceviri PR'lari memnuniyetle karsilanir.
# Quarkus Development Patterns
Quarkus 3.x architecture and API patterns for cloud-native, event-driven services with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: Quarkus Security best practices for authentication, authorization,
origin: ECC
---
> **Not / Note**: Bu dosya henuz Turkceye cevrilmemistir, su anda Ingilizce orijinaldir. Ceviri PR'lari memnuniyetle karsilanir.
# Quarkus Security Review
Best practices for securing Quarkus applications with authentication, authorization, and input validation.

View File

@@ -4,6 +4,8 @@ description: Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito,
origin: ECC
---
> **Not / Note**: Bu dosya henuz Turkceye cevrilmemistir, su anda Ingilizce orijinaldir. Ceviri PR'lari memnuniyetle karsilanir.
# Quarkus TDD Workflow
TDD guidance for Quarkus 3.x services with 80%+ coverage (unit + integration). Optimized for event-driven architectures with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: "Verification loop for Quarkus projects: build, static analysis, te
origin: ECC
---
> **Not / Note**: Bu dosya henuz Turkceye cevrilmemistir, su anda Ingilizce orijinaldir. Ceviri PR'lari memnuniyetle karsilanir.
# Quarkus Verification Loop
Run before PRs, after major changes, and pre-deploy.

View File

@@ -4,6 +4,8 @@ description: Quarkus 3.x LTS architecture patterns with Camel for messaging, RES
origin: ECC
---
> **Note / 注意**: 本文件尚未翻译为中文,目前为英文原版。欢迎提交翻译 PR。
# Quarkus Development Patterns
Quarkus 3.x architecture and API patterns for cloud-native, event-driven services with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: Quarkus Security best practices for authentication, authorization,
origin: ECC
---
> **Note / 注意**: 本文件尚未翻译为中文,目前为英文原版。欢迎提交翻译 PR。
# Quarkus Security Review
Best practices for securing Quarkus applications with authentication, authorization, and input validation.

View File

@@ -4,6 +4,8 @@ description: Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito,
origin: ECC
---
> **Note / 注意**: 本文件尚未翻译为中文,目前为英文原版。欢迎提交翻译 PR。
# Quarkus TDD Workflow
TDD guidance for Quarkus 3.x services with 80%+ coverage (unit + integration). Optimized for event-driven architectures with Apache Camel.

View File

@@ -4,6 +4,8 @@ description: "Verification loop for Quarkus projects: build, static analysis, te
origin: ECC
---
> **Note / 注意**: 本文件尚未翻译为中文,目前为英文原版。欢迎提交翻译 PR。
# Quarkus Verification Loop
Run before PRs, after major changes, and pre-deploy.