Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Blueprints/UnifiedPackageStructure

From TYPO3Wiki
Jump to: navigation, search

<- Back to blueprints overview

Blueprint: Unified Package Structure

Proposal Unified Folder Structure, Package Handling via Composer for CMS 7
Owner/Starter Benni Mack
Participants/Members -
Status Draft, Discussion, Voting Phase, Accepted, Declined, Withdrawn
Current Progress Unknown, Started, Good Progress, Bad Progress, Stalled, Review Needed
Topic for Gerrit ###gerrit_topic###

Target Versions/Milestones

  • Started during TYPO3 CMS 7 development

Goals / Motivation

The goal is to find proper ways to put site specific settings in a composer-based folder structure. The motivation is to unify the handling and location of files, extensions, packages and artifacts.

Concept

Move typo3conf/ data into Configuration/Settings.php and to Packages/VendorName/MyExtension/ - also create a Packages/Sites/Default/ for saving all site-specific information. Additionally, the extensions are just handled as regular composer packages, which completely allows for

Implementation Details

Step 1

Static Resources

Static resources are all files in typo3conf/ext/ and inside typo3/. The core references should be unified. PATH_typo3_mod can be removed then :)

Extension Manager

TODO

Folder Structure

TODO

Risks

Issues and reviews

Dependencies upon other Blueprints