Message-ID: <1314297782.3232.1485852470512.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3231_531577094.1485852470512" ------=_Part_3231_531577094.1485852470512 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Since release 2015.10, eZ Platform is very close to the standard Symfony distribution. It comes with default set= tings that will let you get started in a few minutes.
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, etc.) can be placed there.
Reusable libraries should be packaged so that they can easily be m= anaged using Composer.
Project templates should go into app/Resources/views.
They can then be referenced in code without any prefix, for exampl=
e app/Resources/views/content/full.html.twig
can be refer=
enced in twig templates or PHP as content/full.html.twig
.=
Project assets should go into the web
folde=
r, and can be referenced as relative to the root, for example web/js/=
script.js
can be referenced as js/script.js
from t=
emplates.
Configuration may go into app/config
. However, services def=
initions from AppBundle
should go into src/App=
Bundle/Resources/config
.
The recommended method is to version the whole ezplatform repository. Pe=
r installation configuration should use parameters.yml
.=
p>