The Hidden Dangers of Beautiful Themes

Re:The Hidden Dangers of Beautiful Themes by samarudge on Monday April 23, 2012 @06:08AM (#3878065)

W3 Total Cache plugin for Wordpress will combine all CSS and Javascript files into two requests, you can also use something like NGINX, or even better a proper CDN, for serving static resources.

[ Parent | on HN ]

Re:The Hidden Dangers of Beautiful Themes by dogweather on Monday April 23, 2012 @07:37AM (#3878268)

Thank you - that was an excellent suggestion. I didn't know about this plugin. For sure, one needs to make sure the theme / site is efficiently designed, but this plugin is exceptional. It pretty much does everything I've done by hand on Rails projects.

[ Parent | on HN ]

Re:The Hidden Dangers of Beautiful Themes by ovi256 on Monday April 23, 2012 @08:49AM (#3878466)

Rails 3 has an asset pipeline that does the same thing as that W3 plugin: gathers js/css assets in one file each by default. I can't emphasize enough the "by default" part. It's a very nice default.

[ Parent | on HN ]

Re:The Hidden Dangers of Beautiful Themes by polyfractal on Monday April 23, 2012 @09:32AM (#3878663)

This is a great plugin and pretty easy to use - but be warned: many plugins will not work when W3T's minifying is turned on. W3T does what it can to minimize the conflicts and a few plugins are built with a W3T "compatibility" mode...but many just simply break.

That said, W3T is really great for caching and CDN setup...takes like ten minutes to get going.

[ Parent | on HN ]