At the time of original creation the javascript / css was specific per page, after that per instance per page and so on. Keeping the css/js in one location provided simple all in one template without external dependencies or more complicated implementation(s) at the time.

I think agree that in general it is a good best practice to separate css and js out of templates.

Cheers,
Heath

Hello Lazaro,

I have not had a chance to use yui carousel individually yet in general I like the yui projects.

This extension really provides so little in terms of source code yet itself remains a simple example of combining a javascript library within a design extension with custom templates which use the library api with ezpublish templates custom code which provide data from ezpublish to the javascript library as used within the various templates.

In a way it's nice that the solution to implementing this kind of functionality within eZ Publish can be so simple indeed enjoyable to work with (rather than against). And this is really just the tipping point of what can be done with javascript (as seen through various other similar javascript enabled extension within projects.ez.no).

If you would like to request membership to the project at, http://projects.ez.no/bccarousel/team/members

Then you can submit modifications through subversions using your ez.no username and password.

Update: Apologies for the lateness of my reply.

Cheers,
Heath