[Flow] Best practice: How to organise packages within a flow application

[Qbus | Axel Wüstemann]

Thank you Robert. In my case only this creterion might fit: "plugin 
which should be possible to install optionally."

Would you additionally give me a hint, how to access central ressources, 
as layouts or themes from other (plugin) packages?

Axel

Am 13.05.2013 15:08, schrieb Robert Lemke:
> Hi Axel,
>
> Qbus | Axel Wüstemann wrote:
>
>> what might be a best practice to organise an application in flow? If I
>> have several application components, each of them might consists of
>> modules and plugins etc.
>>
>> Is it good practise to build each applicaion item as a separate flow
>> package? How I can access central ressources of the application from a
>> component package like layout templates, theme files etc.?
>
> I would keep the amount of packages to a minimum as each additional
> package generates overhead in terms of additional Git repository, issue
> tracker and so on.
>
> My criteria for extracting functionality into a separate package:
>
>   - is it standalone / decoupled enough so it could be used in a
> different project?
>   - would it simplify the work of another team / developer if it was a
> dedicated package?
>   - is it a plugin which should be possible to install optionally?
>   - is my main package really too bloated so it needs to be split up?
>
> If any of these matches, I'll create a separate package.
>
> Cheers,
> Robert
>