pimcore
diff --git a/‎README.md‎
Lines changed: 37 additions & 32 deletions b/‎README.md‎
Lines changed: 37 additions & 32 deletions
diff --git a/‎doc/01_Installation.md‎
Lines changed: 0 additions & 103 deletions b/‎doc/01_Installation.md‎
Lines changed: 0 additions & 103 deletions
diff --git a/‎doc/03_Upgrade.md‎ ‎doc/01_Installation/01_Upgrade.md‎doc/03_Upgrade.md renamed to doc/01_Installation/01_Upgrade.md
Lines changed: 31 additions & 16 deletions b/‎doc/03_Upgrade.md‎ ‎doc/01_Installation/01_Upgrade.md‎doc/03_Upgrade.md renamed to doc/01_Installation/01_Upgrade.md
Lines changed: 31 additions & 16 deletions
@@ -1,41 +1,46 @@
 ---
 title: Data Importer
 ---
- 
+
 # Pimcore Data Importer
 
-This extension adds a comprehensive import functionality to Pimcore Datahub. It allows importing data from external 
-sources and adjusting it to Pimcore Data Objects based on a configured mapping without writing any code.
-
-## Features in a Nutshell
-- Multiple imports configuration directly in Datahub. 
-- Data import from various data sources.
-- Supported File Formats: `csv`, `xlsx`, `json`, `xml`.
-- Strategies configuration for: 
-  - loading existing elements for updating data.
-  - defining location for newly imported data.
-  - publishing data.
-  - cleanup of existing data. 
--  Mappings definition for adjusting data to Pimcore Data Objects with:
-   - simple transformations.
-   - preview of imported data.
-- Imports execution directly in Pimcore Datahub or on a regular base via cron definitions. 
-- Import status updates and extensive logging information. 
+The Data Importer adds import functionality to Pimcore Datahub. It reads data from external sources and writes it into
+Pimcore data objects based on a configured mapping, without writing code.
 
 ![Mapping](./doc/img/mapping.png)
 *Mapping and preview of data*
 
-## Documentation Overview
-- [Installation](./doc/01_Installation.md)
-- [Configuration](./doc/03_Configuration/README.md)
-- [Import Execution Details](./doc/04_Import_Execution_Details.md)
-- [Import Progress and Logging](./doc/05_Import_Progress_and_Logging.md)
-- [Extending](./doc/06_Extending/README.md)
-- [Troubleshooting/FAQ](./doc/06_Troubleshooting_FAQ.md) 
-
-## Further Information
-On other Pimcore Datahub adapters and export solutions:
-- [Datahub (GraphQL API)](https://pimcore.com/docs/platform/Datahub/)
-- [Datahub Simple Rest API](https://pimcore.com/docs/platform/Datahub_Simple_Rest/)
--  [Datahub File Export](https://pimcore.com/docs/platform/Datahub_File_Export/)
-- [Datahub Productsup](https://pimcore.com/docs/platform/Datahub_Productsup/)
+## Features
+
+- Import configurations managed directly in Datahub, edited in Pimcore Studio.
+- Six data sources: asset, upload, HTTP, SFTP, push endpoint, and SQL.
+- Five file formats: CSV, JSON, XML, XLSX, and SQL query results.
+- Resolver strategies that decide whether a record updates an existing data object or creates a new one, where it is
+  stored, and whether it is published.
+- A mapping editor with a live preview of the source data and of every transformation step.
+- Delta check to skip unchanged records, and cleanup to remove data objects that left the source.
+- Manual, scheduled, command-line and push-triggered execution.
+- Progress tracking and detailed import logs.
+
+## Documentation
+
+Start here:
+
+- [Installation](./doc/01_Installation/README.md): install the bundle and set up queue processing.
+- [Getting Started](./doc/02_Getting_Started.md): build a first import end to end.
+
+Reference:
+
+- [Configuration](./doc/03_Configuration/README.md): every option of an import configuration.
+- [Import Execution Details](./doc/04_Import_Execution_Details.md): what happens between the trigger and the data.
+- [Import Progress and Logging](./doc/05_Import_Progress_and_Logging.md): watch and audit an import.
+- [Extending](./doc/06_Extending/README.md): custom strategies and events.
+- [Troubleshooting / FAQ](./doc/08_Troubleshooting_FAQ.md): common problems.
+- [Upgrade Notes](./doc/01_Installation/01_Upgrade.md): breaking changes per release.
+
+## Other Datahub Adapters
+
+- [Datahub (GraphQL API)](https://github.com/pimcore/data-hub/blob/2026.x/doc/01_Installation_and_Upgrade/README.md)
+- [Datahub Simple REST API](https://github.com/pimcore/data-hub-simple-rest/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub File Export](https://github.com/pimcore/data-hub-file-export/blob/2026.x/doc/01_Installation/README.md)
+- [Datahub Productsup](https://github.com/pimcore/data-hub-productsup/blob/2026.x/doc/01_Installation/README.md)
@@ -1,4 +1,9 @@
-# Update Notes
+---
+title: Upgrade Notes
+description: Breaking changes and migration steps per release.
+---
+
+# Upgrade Notes
 
 ## Upgrade to 2026.1.0
 
@@ -9,15 +14,19 @@
 
 ### Removed Admin Classic / ExtJS UI
 
-- Removed `pimcore/admin-ui-classic-bundle` dependency. The bundle no longer implements `PimcoreBundleAdminClassicInterface` or uses `BundleAdminClassicTrait`.
-- Removed all ExtJS-based JavaScript and CSS paths (`getCssPaths()`, `getJsPaths()` methods removed from `PimcoreDataImporterBundle`).
+- Removed the `pimcore/admin-ui-classic-bundle` dependency. The bundle no longer implements
+  `PimcoreBundleAdminClassicInterface` and no longer uses `BundleAdminClassicTrait`.
+- Removed all ExtJS-based JavaScript and CSS paths. `getCssPaths()` and `getJsPaths()` were removed from
+  `PimcoreDataImporterBundle`.
 - `PimcoreAdminBundle` is no longer registered as a dependent bundle.
-- The Admin UI configuration panel is now implemented using the Pimcore Studio UI.
-- `Pimcore\Bundle\AdminBundle\Helper\QueryParams` is no longer used; replaced by `DataTypeServiceInterface::extractSortingSettings()`.
+- The configuration panel is now implemented in Pimcore Studio.
+- `Pimcore\Bundle\AdminBundle\Helper\QueryParams` is no longer used. It was replaced by
+  `DataTypeServiceInterface::extractSortingSettings()`.
 
-### Studio UI
+### Pimcore Studio
 
-- Added Studio UI implementation for the Data Importer configuration panel (tabs: Data Setup, Execution, Import Logs).
+- Added the Pimcore Studio implementation of the Data Importer configuration panel, with the tabs Data Setup,
+  Execution and Import Logs.
 - Studio frontend assets are now shipped with the bundle.
 
 ### Namespace Changes
@@ -26,23 +35,28 @@
 
 ### Messenger Transport Configuration
 
-- The messenger transport DSN is now configurable via the `%pimcore.messenger.transport_dsn_prefix%` container parameter instead of being hardcoded to `doctrine://default`. This allows the installer to wire the transport DSN from environment variables (e.g. `PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX`).
+- The messenger transport DSN is configurable via the `%pimcore.messenger.transport_dsn_prefix%` container parameter
+  instead of being hardcoded to `doctrine://default`. The installer can now wire the transport DSN from environment
+  variables such as `PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX`.
 
 ### Interface & Return Type Changes
 
-- `DataTypeServiceInterface`: Added new method `extractSortingSettings(?string $sort): array` to the interface. Any custom implementations of `DataTypeServiceInterface` must implement this method.
+- `DataTypeServiceInterface`: added the method `extractSortingSettings(?string $sort): array`. Custom implementations
+  of the interface must implement it.
 - `CronValidationResponse::isValid(): bool` renamed to `CronValidationResponse::getIsValid(): bool`.
 - `ImportProgressResponse::isRunning(): bool` renamed to `ImportProgressResponse::getIsRunning(): bool`.
-- `PimcoreDataImporterBundle::getInstaller()` return type changed from `?InstallerInterface` to `InstallerInterface` (non-nullable).
+- `PimcoreDataImporterBundle::getInstaller()` return type changed from `?InstallerInterface` to
+  `InstallerInterface` (non-nullable).
 
 ### Class Visibility & Finalization
 
 - Many classes have been marked `final` and/or `@internal`. Custom subclasses of these classes are no longer supported:
-  - `CronScheduler`, `JobScheduler`, `SchedulerFactory` — marked `final` and `@internal`
-  - `PreviewData` — marked `final` and `@internal`
-  - `PimcoreDataImporterBundle` — marked `final`
-  - Various exception classes (`InvalidScheduleException`, etc.) — marked `final`
-- Several `protected` methods on final classes have been changed to `private`. If you were overriding these methods in subclasses, you must refactor.
+  - `CronScheduler`, `JobScheduler`, `SchedulerFactory`: marked `final` and `@internal`
+  - `PreviewData`: marked `final` and `@internal`
+  - `PimcoreDataImporterBundle`: marked `final`
+  - Various exception classes (`InvalidScheduleException`, etc.): marked `final`
+- Several `protected` methods on final classes were changed to `private`. Subclasses overriding them have to be
+  refactored.
 - `ConfigDataObjectController::saveAction()` return type changed from `?JsonResponse` to `JsonResponse` (non-nullable).
 - `Installer::getLastMigrationVersionClassName()` return type changed from `?string` to `string` (non-nullable).
 
@@ -56,7 +70,8 @@
 
 ### API Schema Changes
 
-- `UnitDataResponse`: Schema property renamed from `UnitList` to `unitList` (camelCase). If you consume this API response, update your client accordingly.
+- `UnitDataResponse`: the schema property was renamed from `UnitList` to `unitList`. Update clients consuming this
+  response.
 
 ## Update to Version 1.11