Per the discussion at the Services Sync:
Most CSS will be efficiently handled by the clients…
- Marvin can do this with isomorphic JS so that it will be inlined on first load, but then handled by the client on subsequent loads.
- Apps can pack this in and/or download it separately
But for CSS specific to a template or page, it may be best to inline this in the content. We should see if this is viable and check out implications for the clients.