It should not contain js / css libs in Resources/public folders

[docteurklein]

Currently, we store 2 or 3 jquery versions :)

It would be cool to delegate this to bower (or any other package manager).
The bundle itself doesn't need js/css BTW.
an application does.
That's why I propose to move all this to rad-edition.

[docteurklein]

see KnpLabs/rad-edition#24

[Nek-]

I suggest to use npm/bower for js/css dependencies. ( I love this little class: https://github.com/yohang/dependency-tools )

[docteurklein]

composer is good for managing php deps, not npm install commands.

you could use the SpBowerBundle as a way to interact with bower. Not sure if that's the best one or not though.

[Nek-]

@jrobeson This look like the solution I suggested. But it will not be implemented.

Just a little notice about alternatives: https://github.com/components/components

there's a another solution on the horizon if some composer modifications get merged.

https://github.com/francoispluchino/composer-asset-plugin

[docteurklein]

I'm not sure if I'm right, but I'm all for a pure frontend solution for frontend assets, and composer for backend.

Separation is the keyword.
In an ideal world, front and back would be separated in 2 different projects :)

[akovalyov]

Frontend assets should not be provided by a bundle (I mean common ones like jquery and so on), because it is not bundle-specific but application-specific, in this case project developers should decide the way of maintaining the assets (bower, SpBowerBundle, hard copypaste whatever) _themselves_. https://github.com/knplabs/rad-edition solves this issue via bower and it is completely enough, I think. What RAD Bundle can offer is a helper or some template where developer can specify the location of templates and it will be included in all other RAD templates.