Integration of grunt uncss in autoptimize

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Frank Goossens

    (@futtta)

    8 years, 4 months ago

    hmmm …

    * advantages: smaller CSS
    * disadvantage: unCSS will potentially create different CSS for each page/ blogpost/ … so a different autoptimized unCSS’ed CSS-file will have to be loaded so no autoptimized CSS from browser cache (and more files cached on the server).
    * weakness: need nodeJS + phantomJS + unCSS but AO is PHP-only

    so I’m afraid this isn’t likely to be going to happen soon Amir 🙂

    frank

    Thread Starter tabasco86

    (@tabasco86)

    8 years, 4 months ago

    Ok sure,

    thanks for that input! I just figured it could potentially be a good idea if compatible.
    So what you mean is that if I get grunt and uncss to work it wouldn’t really be compatible with autoptimize? (Cause in that case I’ll abort all attempts).

    Amir

    Plugin Author Frank Goossens

    (@futtta)

    8 years, 4 months ago

    the disavantage mentioned might not be correct, as it seems uncss takes a list of URL’s and creates one CSS-file valid for all. still not easily integratable with AO though, as AO works on a per-request/response level, whereas unCSS works on a site-level (well, a collection of URL’s).

    this does mean, however, that unCSS’ing your theme’s CSS at production-time and having AO optimize CSS (your theme CSS + CSS of plugins) at run-time does make sense.

    frank

    Thread Starter tabasco86

    (@tabasco86)

    8 years, 4 months ago

    Ok,

    thanks a lot Frank. In case you ever decide to make any attempt at creating an additional plugin for this I’ll be the first to download it 😉

    Have a nice day and thanks for your feedback. In this case I’ll try to figure out how to uncss my pre-ao css file.

    Cheers,
    Amir

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Integration of grunt uncss in autoptimize’ is closed to new replies.