Should all of community-platform's CSS be in this project?

Currently, there is CSS in community-platform-static (cool) but also spread across community-platform in various places:

Styles in perl

Styles in templates

Styles in files

So, while individual "applications" in the duck.co space will have their own style requirements, I'm thinking anything that's a "main site" style should be here.

This brings me onto the next question:

Should this project's maintenance / release be off DuckPAN?

Using a CPAN to distribute CSS strikes me as A Bad Thing, if only because our nginx config winds up relying on the currently deployed Perl version...

Also, integrating with this project for development is a bit grey - it's not immediately obvious the best way to do it.

I'm thinking these files should be part of the DDGC package and that they should exist in the development community-platform insance. Git submodules are kind of bad, but might work. Anything. Bound mount. Symlink. cp. OK, not cp.

Something that makes community-platform-static's existence more obvious and easier to work with.

//cc @sdougbrown @thm @zekiel @russellholt @MariagraziaAlastra @jdorweiler