Message-ID: <1141685403.3550.1485853608610.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3549_899365377.1485853608610" ------=_Part_3549_899365377.1485853608610 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html How to structure an eZ Platform project

How to structure an eZ Platform project

Since release 2015.10, eZ Platform is very close from the standard Symfony distribution. It comes with default se= ttings that will let you get started in a few minutes.

The AppBundle

Most projects can use the provided AppBundle, in the&n= bsp;src folder. It is enabled by default. The project's PHP co= de (controllers, event listeners, ...) can be placed there. 

Reusable libraries should be packaged so that they can easily be m= anaged using composer.

Templates

Project templates should go into ezpublish/Resources/vi= ews.

They can then be referenced in code without any prefix: ezpublish/Resources/views/content/full.html.twig can be refere= nced in twig templates or PHP as content/full.html.twig.<= /span>

Assets

Project assets should go into the web folde= r, and can be referenced as relative to the root: web/js/script.= js can be referenced as js/script.js from template= s.

Configuration

Configuration may go in ezpublish/config. However, ser= vices definitions from AppBundle should go into src/AppBundle/Resources/config.

Versioning = a project

The recommended method is to version the whole ezplatform repository. Pe= r installation configuration should use parameters.yml.

------=_Part_3549_899365377.1485853608610--