diff --git a/docs/index.html b/docs/index.html
index 1e11d23e..174e0e8c 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -735,6 +735,30 @@ <h2 id="section-architecture-constraints">2. Architecture Constraints</h2>
 </div>
 </div>
 </div>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>Programming Language Restriction:</strong>
+The system must be implemented using Java as the primary programming language.</p>
+</li>
+<li>
+<p><strong>Mandatory Usage of WikiData API:</strong>
+The WikiData API must be utilized as an integral part of the system, and interactions with WikiData are obligatory for data retrieval and integration.</p>
+</li>
+<li>
+<p><strong>Web Frontend Requirement:</strong>
+The system must include at least one web frontend, and it is mandatory for deployment.</p>
+</li>
+<li>
+<p><strong>Freedom in Database Selection:</strong>
+There are no imposed restrictions on the choice of the database. Teams have the freedom to select a suitable database technology based on project requirements.</p>
+</li>
+<li>
+<p><strong>No Company Policy Constraints:</strong>
+There are no specific constraints or restrictions related to company policies. Teams have the flexibility to make decisions aligned with project goals.</p>
+</li>
+</ul>
+</div>
 <div style="page-break-after: always;"></div>
 </div>
 </div>
diff --git a/docs/src/02_architecture_constraints.adoc b/docs/src/02_architecture_constraints.adoc
index 226e501f..070d697c 100644
--- a/docs/src/02_architecture_constraints.adoc
+++ b/docs/src/02_architecture_constraints.adoc
@@ -25,3 +25,19 @@ conventions (e.g. programming or versioning guidelines, documentation or naming
 See https://docs.arc42.org/section-2/[Architecture Constraints] in the arc42 documentation.
 
 ****
+
+
+- *Programming Language Restriction:*
+  The system must be implemented using Java as the primary programming language.
+
+- *Mandatory Usage of WikiData API:*
+  The WikiData API must be utilized as an integral part of the system, and interactions with WikiData are obligatory for data retrieval and integration.
+
+- *Web Frontend Requirement:*
+  The system must include at least one web frontend, and it is mandatory for deployment.
+
+- *Freedom in Database Selection:*
+  There are no imposed restrictions on the choice of the database. Teams have the freedom to select a suitable database technology based on project requirements.
+
+- *No Company Policy Constraints:*
+  There are no specific constraints or restrictions related to company policies. Teams have the flexibility to make decisions aligned with project goals.