Daniel Siepmann
bbf7ada1d2
That's necessary as models grow. Added features should be tested to not break with future changes. The tests revealed an existing error in fallback which got fixed to make new test pass. Relates: #18 |
||
---|---|---|
.github/workflows | ||
Classes | ||
Configuration | ||
Resources | ||
Tests | ||
.gitignore | ||
composer.json | ||
dependency-checker.json | ||
ecs.php | ||
ext_emconf.php | ||
ext_localconf.php | ||
ext_tables.php | ||
ext_tables.sql | ||
ext_typoscript_setup.typoscript | ||
phpstan-baseline.neon | ||
phpstan.neon | ||
phpunit.xml.dist | ||
README.md |
ThüCAT integration into TYPO3 CMS
ThüCAT is ¨Thüringer Content Architektur Tourismus¨. This is an extension for TYPO3 CMS (https://typo3.org/) to integrate ThüCAT. The existing API is integrated and allows importing data into the system.
Current state
The extension already allows:
-
Create static configuration to import specified resources, e.g. defined organisation or towns.
-
Support multiple languages
-
Import of the following types (not all properties are supported):
-
Organisations (responsible for content)
-
Towns
-
Tourist information
-
Tourist attraction
-
-
Backend module:
-
To inspect current existing organisations and their towns and tourist information
-
To inspect import configuration
-
To create import configuration
-
To inspect past imports and possible errors, as well as number of affected records
-
-
Frontend:
-
Content element to display tourist attraction
-
Page Type to reference tourist attraction
-
Short time goals
-
Content element to display town, tourist information and organisation.
-
Extending import to include further properties