Streamline writing of destination (#38)

werkraum-media · Aug 10, 2023 · de38d80 · de38d80
1 parent 5af1d08
commit de38d80
Show file tree

Hide file tree

Showing 8 changed files with 25 additions and 17 deletions.
diff --git a/Documentation/Changelog/2.5.0.rst b/Documentation/Changelog/2.5.0.rst
@@ -31,7 +31,7 @@ Features
 
   * ``getEndsOnSameDay()``
 
-* Add destination data "Features" to events.
+* Add destination.one "Features" to events.
   Features are again TYPO3 categories with different parent as existing categories.
   New features are hidden by default but can be activated within TYPO3.
   That allows to fetch all within controller and provide them as filter.

diff --git a/Documentation/Changelog/3.1.0.rst b/Documentation/Changelog/3.1.0.rst
@@ -37,7 +37,7 @@ Fixes
 
   Relates: #10253
 
-* Support import of png images from Destination One.
+* Support import of png images from destination.one.
 
 * Do not break TYPO3 v11.5 extension compatibility check.
   The ``addStaticFile()`` method has to be called from ``Configuration/TCA/Overrides/`` instead of ``ext_tables.php`` as this might break frontend.

diff --git a/Documentation/Changelog/3.4.0.rst b/Documentation/Changelog/3.4.0.rst
@@ -6,7 +6,7 @@ Manual steps
 
 * Determining global_id of locations has changed.
   An Update Wizard is provided in order to migrate existing data.
-  This is only necessary when using the import of locations from Destination One.
+  This is only necessary when using the import of locations from destination.one.
 
 Breaking
 --------
@@ -39,7 +39,7 @@ Features
   Only dates with a start date in the future will be shown.
 
 * Handle changes to images for events.
-  The import of destination data one only added new images but kept existing images untouched.
+  The import of destination.one only added new images but kept existing images untouched.
   This was now improved. The import now will update, remove and re-sort images as well.
   Existing image files won't be downloaded again, only information and position are updated.
 
@@ -81,7 +81,7 @@ Fixes
   Those might not exist in newer systems where migration is not necessary.
   The wizard now properly checks for existence before querying the data.
 
-* Prevent duplicate location entries from Destination One import.
+* Prevent duplicate location entries from destination.one import.
   They seem to differ in writing of latitude and longitude.
   An update wizard is provided to clean up existing duplicates.
 

diff --git a/Documentation/Changelog/3.5.0.rst b/Documentation/Changelog/3.5.0.rst
@@ -9,7 +9,7 @@ Nothing
 Features
 --------
 
-* Add PSR-14 Events to Destination Data One import.
+* Add PSR-14 Events to destination.one import.
   They allow individual installation to alter the import.
 
   See :ref:`psr14` for an overview of PSR-14 Events.
@@ -19,7 +19,7 @@ Features
   * Allow to modify an event object before importing.
 
 * Add source to events.
-  Destination Data One provides the original source, either them self or an external.
+  destination.one provides the original source, either them self or an external.
   This is now saved in order to make it easier for editors and companies to contact
   the original source and ask to fix broken data.
 
@@ -35,7 +35,8 @@ Fixes
 Tasks
 -----
 
-Nothing
+* Renaming different Destination cases to destination.one throughout documentation and text.
+  Code is left untouched in order to not break things.
 
 Deprecation
 -----------

diff --git a/Documentation/Features/ImportDestinationOne.rst b/Documentation/Features/ImportDestinationOne.rst
@@ -1,11 +1,11 @@
-.. index:: single: import; DestinationOne
-           single: DestinationOne
+.. index:: single: import; destination.one
+           single: destination.one
 .. _importDestinationOne:
 
-Import Destination One
+Import destination.one
 ======================
 
-The extension provides out of the box to import events from Destination Data One.
+The extension provides out of the box to import events from destination.one.
 
 The import can fetch events, dates, categories and images.
 Multiple imports can be defined, e.g. one per experience.

diff --git a/Documentation/Features/PSR14Events.rst b/Documentation/Features/PSR14Events.rst
@@ -4,10 +4,10 @@
 PSR-14 Events
 =============
 
-.. index:: single: PSR-14 Events; Destination Data One Import: Event Import
+.. index:: single: PSR-14 Events; destination.one Import: Event Import
 
-Destination Data One Import: ``EventImportEvent``
--------------------------------------------------
+destination.one Import: ``EventImportEvent``
+--------------------------------------------
 
-Executed during Destination Data One Import.
+Executed during destination.one Import.
 Allows to alter the event prior persistence.
diff --git a/README.rst b/README.rst
@@ -7,3 +7,6 @@ This is shared as is. It is developed and used by the agency for some years alre
 The code and test coverage dates back some years.
 We continuously try to improve the overall situation.
 Don't expect heavy documentation at this state.
+
+The main benefit is an import of destination.one events into TYPO3. More info: https://www.destination.one/
+You might find old references to "destination data" within the code as there was a rebranding.
diff --git a/composer.json b/composer.json
@@ -2,7 +2,11 @@
     "name": "wrm/events",
     "type": "typo3-cms-extension",
     "license": "GPL-2.0-or-later",
-    "description": "Extension to manage Destination Data managed events",
+    "description": "Extension to manage destination.one managed events",
+    "keywords": [
+        "events",
+        "destination.one"
+    ],
     "authors": [
         {
             "name": "Dirk Koritnik",