Message-ID: <651854840.3162.1485852245796.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3161_1741239234.1485852245796" ------=_Part_3161_1741239234.1485852245796 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
eZ CMS is based on the Symfony2 framework and follows its organi= zation of the app. Like in Symfony, where "every= thing is a bundle", your eZ application is going to be a collection of = bundles.
A bundle in Symfony (and eZ) is a separate part of your application that= implements a feature. You can create bundles yourself or make use of avail= able open-source bundles. You can also reuse the bundles you create in othe= r projects or share them with the community.
Many eZ CMS functionalities are provided through separate bundles includ= ed in the installation. See = Bundles reference for a reference of the included bundles.
By default, a clean eZ Platform installation contains an AppBundle where= you can place your code.
To learn more about organizing your eZ project, see Structuring an eZ project.
You can generate a new bundle using a generate:bundle
comma=
nd. See Symfony documentation on generating bundles.