docs: update README(_FR).md and CHANGELOG.md

Author: btouchard

CHANGELOG.md

@@ -5,6 +5,70 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.3] - 2025-10-08
+
+### Added
+- **Document Metadata Management System**
+  - New `documents` table for storing metadata (title, URL, checksum, description)
+  - Document repository with full CRUD operations
+  - Comprehensive integration tests for document operations
+  - Admin UI section for viewing and editing document metadata
+  - Copy-to-clipboard functionality for checksums
+  - Support for SHA-256, SHA-512, and MD5 checksum algorithms
+  - Automatic `updated_at` timestamp tracking with PostgreSQL trigger
+
+- **Modern Modal Dialogs**
+  - Replaced native JavaScript `alert()` and `confirm()` with styled modal dialogs
+  - Consistent design across all confirmation actions
+  - Better UX with warning (orange) and delete (red) visual indicators
+  - Confirmation modal for email reminder sending
+  - Delete confirmation modal for removing expected readers
+
+- **SVG Favicon**
+  - Added modern vector favicon with brand identity
+  - Responsive and works across all modern browsers
+
+### Changed
+- **Email Reminder Improvements**
+  - Email language now matches user's interface language (fr/en)
+  - Document URL automatically fetched from metadata instead of manual input
+  - Simplified reminder form by removing redundant URL field
+  - Document URL displayed as clickable link in reminder section
+
+- **Admin Dashboard Enhancement**
+  - Document listing now includes documents from `documents` table
+  - Shows documents with metadata even without signatures or expected readers
+
+- **UI Refinements**
+  - Removed "Admin connecté" status indicator from dashboard header
+  - Document URL in metadata displayed as hyperlink instead of input field
+  - Cleaner and more focused admin interface
+
+### Fixed
+- Template syntax error with `not` operator requiring parentheses
+
+### Technical Details
+- Added database migration `0005_create_documents_table`
+- New domain model: `models.Document` and `models.DocumentInput`
+- New infrastructure: `DocumentRepository` with full test coverage
+- New presentation: `DocumentHandlers` with GET/POST/DELETE endpoints
+- Routes: `/admin/docs/{docID}/metadata` (GET, POST, DELETE)
+- Updated `ReminderService.SendReminders()` signature to include locale parameter
+- Modified files:
+  - `internal/domain/models/document.go` (new)
+  - `internal/infrastructure/database/document_repository.go` (new)
+  - `internal/infrastructure/database/document_repository_test.go` (new)
+  - `internal/presentation/admin/handlers_documents.go` (new)
+  - `internal/application/services/reminder.go`
+  - `internal/infrastructure/database/admin_repository.go`
+  - `internal/presentation/admin/handlers_expected_signers.go`
+  - `internal/presentation/admin/routes_admin.go`
+  - `templates/admin_dashboard.html.tpl`
+  - `templates/admin_document_expected_signers.html.tpl`
+  - `templates/base.html.tpl`
+  - `static/favicon.svg` (new)
+  - `migrations/0005_create_documents_table.{up,down}.sql` (new)
+
 ## [1.1.2] - 2025-10-03
 
 ### Added
@@ -52,6 +116,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - NULL UserName handling in database operations
 - Proper string conversion for UserName field
 
+[1.1.3]: https://github.com/btouchard/ackify-ce/compare/v1.1.2...v1.1.3
 [1.1.2]: https://github.com/btouchard/ackify-ce/compare/v1.1.1...v1.1.2
 [1.1.1]: https://github.com/btouchard/ackify-ce/compare/v1.1.0...v1.1.1
 [1.1.0]: https://github.com/btouchard/ackify-ce/releases/tag/v1.1.0

README.md

@@ -254,11 +254,25 @@ CREATE TABLE expected_signers (
     id BIGSERIAL PRIMARY KEY,
     doc_id TEXT NOT NULL,
     email TEXT NOT NULL,
+    name TEXT NOT NULL DEFAULT '',          -- Display name (optional)
     added_at TIMESTAMPTZ NOT NULL DEFAULT now(),
     added_by TEXT NOT NULL,                 -- Admin who added
     notes TEXT,
     UNIQUE (doc_id, email)                  -- One expectation per email/doc
 );
+
+-- Document metadata table
+CREATE TABLE documents (
+    doc_id TEXT PRIMARY KEY,
+    title TEXT NOT NULL DEFAULT '',
+    url TEXT NOT NULL DEFAULT '',           -- Document location
+    checksum TEXT NOT NULL DEFAULT '',      -- SHA-256/SHA-512/MD5
+    checksum_algorithm TEXT NOT NULL DEFAULT 'SHA-256',
+    description TEXT NOT NULL DEFAULT '',
+    created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
+    updated_at TIMESTAMPTZ NOT NULL DEFAULT now(),
+    created_by TEXT NOT NULL DEFAULT ''
+);
 ```
 
 **Guarantees**:
@@ -267,6 +281,7 @@ CREATE TABLE expected_signers (
 - ✅ **Integrity**: SHA-256 hash to detect modifications
 - ✅ **Non-repudiation**: Ed25519 signature cryptographically provable
 - ✅ **Tracking**: Expected signers for completion monitoring
+- ✅ **Metadata**: Document information with URL, checksum, and description
 
 ---
 
@@ -348,6 +363,11 @@ ACKIFY_MAIL_PASSWORD="${SMTP_PASSWORD}"
 - `GET /admin/docs/{docID}` - Document details with expected signers management
 - `POST /admin/docs/{docID}/expected` - Add expected signers
 - `POST /admin/docs/{docID}/expected/remove` - Remove an expected signer
+- `POST /admin/docs/{docID}/reminders/send` - Send email reminders to pending readers
+- `GET /admin/docs/{docID}/reminders/history` - Get reminder history as JSON
+- `GET /admin/docs/{docID}/metadata` - Get document metadata as JSON
+- `POST /admin/docs/{docID}/metadata` - Create or update document metadata
+- `DELETE /admin/docs/{docID}/metadata` - Delete document metadata
 - `GET /admin/docs/{docID}/status.json` - Document status as JSON (AJAX)
 - `GET /admin/api/chain-integrity/{docID}` - Chain integrity verification JSON
 
@@ -356,11 +376,21 @@ Access control: set `ACKIFY_ADMIN_EMAILS` with a comma-separated list of admin e
 ACKIFY_ADMIN_EMAILS="alice@company.com,bob@company.com"
 ```
 
+#### Document Metadata Management
+Administrators can manage comprehensive metadata for each document:
+- **Store document information**: Title, URL/location, checksum, description
+- **Integrity verification**: Support for SHA-256, SHA-512, and MD5 checksums
+- **Easy access**: One-click copy for checksums, clickable document URLs
+- **Automatic timestamps**: Track creation and updates with PostgreSQL triggers
+- **Email integration**: Document URL automatically included in reminder emails
+
 #### Expected Signers Feature
 Administrators can define and track expected signers for each document:
 - **Add expected signers**: Paste emails separated by newlines, commas, or semicolons
+- **Support names**: Use format "Name <email@example.com>" for personalized emails
 - **Track completion**: Visual progress bar with completion percentage
 - **Monitor status**: See who signed (✓) vs. who is pending (⏳)
+- **Email reminders**: Send bulk or selective reminders in user's language
 - **Detect unexpected signatures**: Identify users who signed but weren't expected
 - **Share easily**: One-click copy of document signature link
 - **Bulk management**: Add/remove signers individually or in batch

README_FR.md

@@ -262,11 +262,25 @@ CREATE TABLE expected_signers (
     id BIGSERIAL PRIMARY KEY,
     doc_id TEXT NOT NULL,
     email TEXT NOT NULL,
+    name TEXT NOT NULL DEFAULT '',           -- Nom d'affichage (optionnel)
     added_at TIMESTAMPTZ NOT NULL DEFAULT now(),
     added_by TEXT NOT NULL,                  -- Admin qui a ajouté
     notes TEXT,
     UNIQUE (doc_id, email)                   -- Une attente par email/doc
 );
+
+-- Table des métadonnées de documents
+CREATE TABLE documents (
+    doc_id TEXT PRIMARY KEY,
+    title TEXT NOT NULL DEFAULT '',
+    url TEXT NOT NULL DEFAULT '',            -- Emplacement du document
+    checksum TEXT NOT NULL DEFAULT '',       -- SHA-256/SHA-512/MD5
+    checksum_algorithm TEXT NOT NULL DEFAULT 'SHA-256',
+    description TEXT NOT NULL DEFAULT '',
+    created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
+    updated_at TIMESTAMPTZ NOT NULL DEFAULT now(),
+    created_by TEXT NOT NULL DEFAULT ''
+);
 ```
 
 **Garanties** :
@@ -275,6 +289,7 @@ CREATE TABLE expected_signers (
 - ✅ **Intégrité** : Hachage SHA-256 pour détecter modifications
 - ✅ **Non-répudiation** : Signature Ed25519 cryptographiquement prouvable
 - ✅ **Suivi** : Signataires attendus pour monitoring de complétion
+- ✅ **Métadonnées** : Informations de documents avec URL, checksum et description
 
 ---
 
@@ -356,6 +371,11 @@ ACKIFY_MAIL_PASSWORD="${SMTP_PASSWORD}"
 - `GET /admin/docs/{docID}` - Détails du document avec gestion des signataires attendus
 - `POST /admin/docs/{docID}/expected` - Ajouter des signataires attendus
 - `POST /admin/docs/{docID}/expected/remove` - Retirer un signataire attendu
+- `POST /admin/docs/{docID}/reminders/send` - Envoyer des rappels par email aux lecteurs en attente
+- `GET /admin/docs/{docID}/reminders/history` - Obtenir l'historique des rappels en JSON
+- `GET /admin/docs/{docID}/metadata` - Obtenir les métadonnées du document en JSON
+- `POST /admin/docs/{docID}/metadata` - Créer ou mettre à jour les métadonnées du document
+- `DELETE /admin/docs/{docID}/metadata` - Supprimer les métadonnées du document
 - `GET /admin/docs/{docID}/status.json` - Statut du document en JSON (AJAX)
 - `GET /admin/api/chain-integrity/{docID}` - Vérification d'intégrité de chaîne (JSON)
 
@@ -364,11 +384,21 @@ Contrôle d'accès: définir `ACKIFY_ADMIN_EMAILS` avec des emails admins, sépa
 ACKIFY_ADMIN_EMAILS="alice@entreprise.com,bob@entreprise.com"
 ```
 
+#### Gestion des Métadonnées de Documents
+Les administrateurs peuvent gérer des métadonnées complètes pour chaque document :
+- **Stocker les informations** : Titre, URL/emplacement, checksum, description
+- **Vérification d'intégrité** : Support pour les checksums SHA-256, SHA-512 et MD5
+- **Accès facile** : Copie en un clic pour les checksums, URLs de documents cliquables
+- **Horodatage automatique** : Suivi de la création et des mises à jour avec triggers PostgreSQL
+- **Intégration email** : URL du document automatiquement incluse dans les emails de rappel
+
 #### Fonctionnalité Signataires Attendus
 Les administrateurs peuvent définir et suivre les signataires attendus pour chaque document :
 - **Ajouter des signataires** : Coller des emails séparés par des sauts de ligne, virgules ou point-virgules
+- **Support des noms** : Utiliser le format "Nom <email@example.com>" pour les emails personnalisés
 - **Suivre la complétion** : Barre de progression visuelle avec pourcentage
 - **Monitorer le statut** : Voir qui a signé (✓) vs. qui est en attente (⏳)
+- **Rappels par email** : Envoyer des rappels en masse ou sélectifs dans la langue de l'utilisateur
 - **Détecter les signatures inattendues** : Identifier les utilisateurs qui ont signé sans être attendus
 - **Partage facile** : Copie en un clic du lien de signature du document
 - **Gestion en masse** : Ajouter/retirer des signataires individuellement ou en lot