fix table with handling, icons implemented

docs/INSTALLATION.md

@@ -231,3 +231,58 @@ Check:
 ### A configuration file is missing
 
 If `config.json` or `APPINFO.json` is absent, restart the application container. The entrypoint creates a missing default file without overwriting an existing one.
+
+### Persistent standard image library
+
+Add the following persistent volume to the application service:
+
+```yaml
+- ./data/uploads:/app/app/static/uploads
+```
+
+Create the host directory before the first start if desired:
+
+```bash
+mkdir -p data/uploads/library
+```
+
+Images uploaded through the AssetManager standard image library are stored there. You can also copy PNG, JPG/JPEG, WEBP or GIF files directly into this directory. They are then offered for selection in asset and category forms after the page is reloaded.
+
+
+## Standard image library
+
+Reusable asset/category images are stored persistently on the Docker host in:
+
+```text
+./data/uploads/library
+```
+
+The library is a subdirectory of the already existing uploads volume. No additional Docker mount is required. The existing Compose mapping:
+
+```text
+./data/uploads -> /app/app/static/uploads
+```
+
+therefore exposes the library as:
+
+```text
+Host:      ./data/uploads/library
+Container: /app/app/static/uploads/library
+```
+
+Images may be uploaded from the AssetManager forms or copied directly into `./data/uploads/library` on the Docker host. They remain persistent because `data/uploads` is already part of the standard AssetManager volume layout.
+
+For image-based installations use:
+
+```bash
+docker compose down
+docker compose pull
+docker compose up -d
+```
+
+You can verify the active mount with:
+
+```bash
+```
+
+Images copied directly into `./data/uploads/library` are available in the AssetManager image library after reloading the page.