Many minor changes in markdown for Github pages

Author: bero

docs/classes/TBoldAttribute.md

@@ -6,6 +6,9 @@
 
 ```mermaid
 classDiagram
+    class TBoldMember {
+        <<abstract>>
+    }
     TBoldMember <|-- TBoldAttribute
     TBoldAttribute <|-- TBAString
     TBoldAttribute <|-- TBAInteger
@@ -17,6 +20,8 @@ classDiagram
     TBoldAttribute : +IsNull
     TBoldAttribute : +SetToNull()
     TBoldAttribute : +AsString
+
+    click TBoldMember href "TBoldMember/" "TBoldMember documentation"
 ```
 
 ## Attribute Types

docs/classes/index.md

@@ -55,6 +55,12 @@ classDiagram
     TBoldMember <|-- TBoldObjectReference
     TBoldMember <|-- TBoldObjectList
     TBoldElement <|-- TBoldSystem
+
+    click TBoldSystem "TBoldSystem/" "TBoldSystem documentation"
+    click TBoldObject "TBoldObject/" "TBoldObject documentation"
+    click TBoldObjectList "TBoldObjectList/" "TBoldObjectList documentation"
+    click TBoldMember "TBoldMember/" "TBoldMember documentation"
+    click TBoldAttribute "TBoldAttribute/" "TBoldAttribute documentation"
 ```
 
 ## Core Classes
@@ -85,6 +91,11 @@ flowchart TB
     Object -->|"has members"| List
     Reference -->|"points to"| Object
     List -->|"contains"| Object
+
+    click System "TBoldSystem/" "TBoldSystem documentation"
+    click Object "TBoldObject/" "TBoldObject documentation"
+    click Attribute "TBoldAttribute/" "TBoldAttribute documentation"
+    click List "TBoldObjectList/" "TBoldObjectList documentation"
 ```
 
 ## Common Patterns

docs/concepts/index.md

@@ -31,6 +31,13 @@ flowchart TB
     ObjectSpace --> Subscriptions
     ObjectSpace --> Persistence
     Persistence --> DB
+
+    click ObjectSpace "object-space/" "Object Space documentation"
+    click OCL "ocl/" "OCL documentation"
+    click Subscriptions "subscriptions/" "Subscriptions documentation"
+    click Logging "logging/" "Logging documentation"
+    click Persistence "persistence/" "Persistence documentation"
+    click DB "persistence/" "Database persistence documentation"
 ```
 
 ## Key Concepts

docs/concepts/persistence.md

@@ -3,7 +3,6 @@
 Bold provides transparent **Object-Relational Mapping (ORM)** that automatically persists your domain objects to a relational database.
 
 ## Architecture
-
 ```mermaid
 flowchart LR
     subgraph ObjectSpace["Object Space"]
@@ -37,44 +36,76 @@ flowchart LR
 | Inheritance | Type discriminator column |
 
 ### Example Mapping
+```mermaid
+flowchart LR
+    subgraph UML["UML Model"]
+        Customer["Customer\n───────────\nName: String\nEmail: String"]
+        Order["Order\n───────────\nOrderDate: Date\nTotal: Currency"]
+        OrderItem["OrderItem\n───────────\nQuantity: Integer"]
+    end
 
+    subgraph DB["Database Schema"]
+        T1["CUSTOMER"]
+        T2["CUSTOMER_ORDER"]
+        T3["ORDER_ITEM"]
+    end
+
+    Customer --> T1
+    Order --> T2
+    OrderItem --> T3
 ```
-UML Model                    Database Schema
-───────────                  ───────────────
-┌─────────────┐              ┌─────────────────────────┐
-│  Customer   │              │ CUSTOMER                │
-├─────────────┤              ├─────────────────────────┤
-│ Name: String│  ────────►   │ BOLD_ID      INT PK     │
-│ Email:String│              │ BOLD_TYPE    INT        │
-└─────────────┘              │ NAME         VARCHAR    │
-                             │ EMAIL        VARCHAR    │
-                             └─────────────────────────┘
+```mermaid
+erDiagram
+    CUSTOMER {
+        INT BOLD_ID PK
+        INT BOLD_TYPE
+        VARCHAR NAME
+        VARCHAR EMAIL
+    }
+    
+    CUSTOMER_ORDER {
+        INT BOLD_ID PK
+        INT BOLD_TYPE
+        INT CUSTOMER_ID FK
+        DATE ORDERDATE
+        DECIMAL TOTAL
+    }
+    
+    ORDER_ITEM {
+        INT BOLD_ID PK
+        INT BOLD_TYPE
+        INT ORDER_ID FK
+        INT PRODUCT_ID FK
+        INT QUANTITY
+    }
+    
+    CUSTOMER ||--o{ CUSTOMER_ORDER : "places"
+    CUSTOMER_ORDER ||--o{ ORDER_ITEM : "contains"
 ```
 
 ## Configuration
 
 ### Database Adapter Setup
-
 ```pascal
 // FireDAC adapter (recommended)
 BoldDatabaseAdapterFireDAC1.Connection := FDConnection1;
 BoldPersistenceHandleDB1.DatabaseAdapter := BoldDatabaseAdapterFireDAC1;
 ```
 
-### Supported Databases
+### Supported Persistence Targets
 
-| Database | Adapter |
-|----------|---------|
+| Target | Adapter |
+|--------|---------|
 | SQL Server | FireDAC, UniDAC |
 | PostgreSQL | FireDAC, UniDAC |
 | InterBase | FireDAC |
 | Oracle | FireDAC, UniDAC |
 | SQLite | FireDAC |
+| XML | BoldPersistenceHandleFileXML |
 
 ## Operations
 
 ### Save Changes
-
 ```pascal
 // Save all dirty objects to database
 BoldSystemHandle1.UpdateDatabase;
@@ -86,7 +117,6 @@ BoldSystemHandle1.System.UpdateDatabase;
 ### Fetch Objects
 
 Bold fetches objects lazily by default:
-
 ```pascal
 // Objects loaded on first access
 Customer := Customers[0];  // Fetches from DB if not loaded
@@ -96,7 +126,6 @@ Name := Customer.Name;     // Attribute already loaded
 ### Batch Fetching
 
 For performance, prefetch related objects:
-
 ```pascal
 // Fetch customers and their orders in one query
 BoldSystemHandle1.System.FetchLinksWithObjects(
@@ -108,7 +137,6 @@ BoldSystemHandle1.System.FetchLinksWithObjects(
 ## Transactions
 
 ### Basic Transaction
-
 ```pascal
 BoldSystem.StartTransaction;
 try
@@ -131,13 +159,13 @@ Bold supports nested transactions with savepoints.
 ## Schema Evolution
 
 Bold can evolve your database schema when the model changes:
-
 ```pascal
 // Use DbEvolutor to generate migration scripts
 BoldDbEvolutor1.GenerateScript;
 ```
 
 Changes handled:
+
 - Add/remove classes (tables)
 - Add/remove attributes (columns)
 - Modify attribute types
@@ -148,4 +176,4 @@ Changes handled:
 1. **Use batch fetching** for collections you'll iterate
 2. **Avoid N+1 queries** by prefetching associations
 3. **Use OCL efficiently** - filter in database when possible
-4. **Index foreign keys** for faster association traversal
+4. **Index foreign keys** for faster association traversal

docs/faq.md

@@ -276,9 +276,11 @@ BoldDbEvolutor1.GenerateScript;
 ### Can I use Bold with an existing database?
 
 Yes, but you need to:
-1. Create a UML model matching the existing schema
-2. Configure table/column mappings in tagged values
-3. Import existing data carefully
+
+1. Create a UML model matching the existing schema.
+2. Create a new database with Bold.
+3. Configure table/column mappings in tagged values.
+4. Import existing data carefully.
 
 ---
 

docs/getting-started/index.md

@@ -21,6 +21,11 @@ graph LR
     B --> C[TBoldObject instances]
     C --> D[TBoldAttribute values]
     C --> E[TBoldObjectReference links]
+
+    click A "../classes/TBoldSystem/" "TBoldSystem documentation"
+    click C "../classes/TBoldObject/" "TBoldObject documentation"
+    click D "../classes/TBoldAttribute/" "TBoldAttribute documentation"
+    click E "../classes/TBoldMember/" "TBoldMember documentation"
 ```
 
 ### Persistence Layer

docs/index.md

@@ -37,6 +37,12 @@ flowchart TB
     System --> OCL
     Objects --> PMapper
     PMapper --> DB
+
+    click System "classes/TBoldSystem/" "TBoldSystem documentation"
+    click Objects "classes/TBoldObject/" "TBoldObject documentation"
+    click OCL "concepts/ocl/" "OCL documentation"
+    click PMapper "concepts/persistence/" "Persistence documentation"
+    click DB "concepts/persistence/" "Database persistence documentation"
 ```
 
 ## Quick Start

mkdocs.yml

@@ -7,8 +7,6 @@ edit_uri: edit/develop/docs/
 
 theme:
   name: material
-  logo: images/boldlogo.png
-  favicon: images/favbold.png
   palette:
     - scheme: default
       primary: indigo