You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, Pimcore-Partners-Agencies implement and sell MANY websites.
We usually use some central bundle with core Model and Services to share among all created websites.
Such bundle is usually connected as vendor/bundle in composer.json
In some special cases, it can be connected as GitSubmodule.
It makes us easier to:
update/bugfix all created website in 1 place
reuse company experience for the new project
speed up new website creation process
What I propose to move to such CentralBundle in Demo application:
the whole content of /src/ folder except car.*
central twig templates. Local ones you can keep, but they will just include central ones -- to allow a developer to overwrite in the future if the project looks different.
CSS files. With only 1 local CSS left
Data-Object interface and definitions. Local Data-Object classes only extends central definitions, so admin can add more fields
Feature description
Usually, Pimcore-Partners-Agencies implement and sell MANY websites.
We usually use some central bundle with core Model and Services to share among all created websites.
Such bundle is usually connected as vendor/bundle in composer.json
In some special cases, it can be connected as GitSubmodule.
It makes us easier to:
What I propose to move to such CentralBundle in Demo application: