doc: update structure of the documentation

Author: brunopacheco1

.gitignore

@@ -25,4 +25,5 @@ yarn-error.log*
 .clj-kondo/
 .lsp/
 .vscode/
-.antigravity/
+.antigravity/
+extracted_text/

docs/architectural-decisions.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 9
+description: Important, expensive, critical, large scale or risky architecture decisions including rationales.
 ---
 
 # Architectural Decisions (ADRs)

docs/constraints.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 2
+description: Anything that constrains teams in design and implementation decisions or decision about related processes. Can sometimes go beyond individual systems and are valid for whole organizations and companies.
 ---
 
 # Constraints

docs/context-and-scope.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 3
+description: Delimits your system from its (external) communication partners (neighboring systems and users). Specifies the external interfaces. Shown from a business/domain perspective (always) or a technical perspective (optional).
 ---
 
 # Context and Scope

docs/crosscutting-concepts.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 8
+description: Overall, principal regulations and solution approaches relevant in multiple parts (→ cross-cutting) of the system. Concepts are often related to multiple building blocks. Include different topics like domain models, architecture patterns and -styles, rules for using specific technology and implementation rules.
 ---
 
 # Cross-cutting Concepts

docs/glossary.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 12
+description: Important domain and technical terms that stakeholders use when discussing the system. Also, translation reference if you work in a multi-language environment.
 ---
 
 # Glossary

docs/introduction-and-goals.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 1
+description: Short description of the requirements, driving forces, extract (or abstract) of requirements. Top three (max five) quality goals for the architecture which have highest priority for the major stakeholders. A table of important stakeholders with their expectation regarding architecture.
 ---
 
 # Introduction and Goals

docs/oneplusmg-infrastructure/_category_.json

@@ -0,0 +1,7 @@
+{
+    "label": "1+MG Infrastructure",
+    "position": 4,
+    "link": {
+        "type": "generated-index"
+    }
+}

docs/oneplusmg-infrastructure/_category_.json.license

@@ -0,0 +1,3 @@
+SPDX-FileCopyrightText: 2025 PNED G.I.E.
+
+SPDX-License-Identifier: Apache-2.0

docs/building-block-view.md …mg-infrastructure/building-block-view.mddocs/building-block-view.md renamed to docs/oneplusmg-infrastructure/building-block-view.md docs/building-block-view.md renamed to docs/oneplusmg-infrastructure/building-block-view.md

@@ -4,6 +4,7 @@
 # SPDX-License-Identifier: CC-BY-4.0
 
 sidebar_position: 5
+description: Static decomposition of the system, abstractions of source-code, shown as hierarchy of white boxes (containing black boxes), up to the appropriate level of detail.
 ---
 
 # Building Block View
@@ -12,8 +13,6 @@ sidebar_position: 5
 
 The 1+MG Infrastructure is decomposed into three primary logical zones:
 
-![Business Context](./assets/business_context.drawio.png)
-
 | System                                | Responsibility                                                                                                                                                                                                                                                                             |
 | :------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **1+MG User Portal (Central)**        | **Functional Description:** The web-based entry point for researchers to discover data and request access.<br/>**Interfaces:** HTTPS (Web), OIDC (Auth), Beacon API (Query).<br/>**Quality:** High Usability, Public Accessibility.<br/>**Location:** `src/portal`, Hosted by Genome EDIC. |