I’ve got two sites and two site packages. My separation - as I thought - was to help making separate module assignments, templates and css/js files available to my different sites under the same typo3 installation. The scaffolding site packages were created via https://sitepackagebuilder.com.
I thought that creating different templates for the different sites and static-including different extensions was enough. However I noticed that all typoscript code is picked up when a fluid template calls for it.
For example, if site B html template calls for lib.sub_pages (<f:cObject typoscriptObjectPath=“lib.sub_pages” />) which is only declared in site A’s site package, site A’s setup.typoscript runs to calculate this module.
Meaning that whatever I run in any “setup.typoscript” affects both sites. This is not what I want to do as I want to have separation of typoscript between the two sites.
So my question is this: If I have multiple site packages, what is shared between them when each package is static-included on each site? If typoscript is all common no matter where each site package is assigned, then is it enough if fluid template calls for different module names (like lib.sub_pages_A and lib.sub_pages_B)? Or is this bad design?
Thank you and sorry for the long text!