Integrating SkillDisplay as content elements into TYPO3. https://www.skilldisplay.eu/
Find a file
Daniel Siepmann 7c4a9820b4
Use composer v1 in CI
Not all dev dependencies are v2 ready.

maglnet/composer-require-checker has a dependency to
ocramius/package-versions version which requires v1 composer API.
Once a newer version is required, we can use v2.
2020-12-01 10:46:02 +01:00
.github/workflows Use composer v1 in CI 2020-12-01 10:46:02 +01:00
Classes Handle unavailable skills and skillsets in backend and frontend 2020-10-05 09:40:54 +02:00
Configuration Integrate CSS and HTML 2020-10-19 11:41:57 +02:00
Resources [TASK] Re-add schema to xliff files 2020-11-27 23:14:26 +01:00
Tests/Unit Handle unavailable skills and skillsets in backend and frontend 2020-10-05 09:40:54 +02:00
.gitignore Add content element "skills" 2020-09-22 10:37:24 +02:00
composer.json Adjust dependency to released toolkit version 2020-10-19 14:51:59 +02:00
ext_emconf.php Add PHP 7.2 compatibility 2020-09-22 13:27:52 +02:00
ext_localconf.php Add content element "skillsets" 2020-09-22 14:17:36 +02:00
ext_tables.sql [BUGFIX] Use valid syntax in ext_tables.sql 2020-11-27 22:52:29 +01:00
phpcs.xml.dist Add unit tests 2020-09-24 08:39:53 +02:00
phpstan.neon Add unit tests 2020-09-24 08:39:53 +02:00
phpunit.xml.dist Add unit tests 2020-09-24 08:39:53 +02:00
README.rst Integrate CSS and HTML 2020-10-19 11:41:57 +02:00

TYPO3 Extension to integrate SkillDisplay

This TYPO3 extension integrates SkillDisplay into TYPO3 installations.

Right now it provides the following features:

  • Content element to render one or more skills.
  • Content element to render one skill set.
  • DataProcessor to fetch skills as entities via API.
  • DataProcessor to fetch skill sets as entities via API.
  • ViewHelper to generate verification button.
  • ViewHelper to generate verification URL.

Installation

The extension can be installed by downloading recent version from GitHub and adding it inside typo3conf/ folder.

Add static TypoScript once installed and activated via Extension Manager. The TypoScript contains the rendering definition for provided content elements.

Next Step: Copy Templates or adjust template paths via TypoScript. In order to allow TYPO3 to find the Fluid templates for content elements, either add the path EXT:skilldisplay/Resources/Private/Templates/ContentElements/ in TypoScript, e.g.:

lib.contentElement {
    partialRootPaths {
        50 = EXT:skilldisplay/Resources/Private/Partials/ContentElements/
    }
    templateRootPaths {
        50 = EXT:skilldisplay/Resources/Private/Templates/ContentElements/
    }
}

Ensure the path has a lower number then your own paths and doesn't overwrite any existing number.

Or copy the files from /Resources/Private/Templates/ContentElements/ to your existing template folder.

Configuration

Site configuration is extended, where options like API Key can be provided.

Also TypoScript and TSconfig is added to provide wizard entries for new content elements, as well as rendering. Both can be adjusted via custom TypoScript and TSconfig.

Usage

Add content elements to the pages and insert the ID of skills as comma separated list, or the ID of a single skill set.