Objectives

short-term objectives

@tristanlins and @dominikzogg searched a way to load third party libraries/components like assetic within contao 2 and 3. As many others like symfony and zendframework we took composer for this task.

Until now, we can load libraries/components with composer and their dependencies, but we can't resolve module dependencies. Composer got a nice feature called composer-installer, this are special dependencies get installed first and allows to create specific installers for specific tasks, like installing contao modules. Cause contao modules can bring different folders and files on different places, its not easy to build one.

• something that loads the composer autoloader done @dominikzogg
• an own composer-installer for contao modules done @tristanlins
• a gui to manage the modules and libraries/components done @tristanlins
• a possibility to use composer without allow_url_fopen inprogress @dominikzogg
• a possibility to use composer without phar support inprogress @tristanlins @discordier
• a way to test this integration (unittesting, testgroup) @dominikzogg
• faq inprogress @dominikzogg
• a module for the extension repository inprogress @tristanlins
• standalone backend to be able to repair defective installations @tristanlins @discordier

medium-term objectives

But there is a problem, whats about all packages installed with the contao extension repository? There is no real solution at the moment (hacking the ER client isn't a good ones ;-)

• find a way to solve dependencies against the extension repository done @discordier
• translatable composer.json within modules
• add screenshots to composer.json

long-term objectives

We hope we find a way to replace the extension repository

• own repository like packagist inprogress @discordier
• assessment system
• download statistics