Implementation for dynamic websites
mattymess opened this issue · comments
This seems like it would work really well for pages that aren't changing very often. However, most of the web is dynamic where the header and footer might be the only things on the page that stay the same throughout the site.
How do you address this use case?
Well, we typically run it on every unique template of a site. While the content within the pages that use that template can vary, the CSS that runs those pages is often stable (hence the unique template part). So... assuming the site is set up like that, that's how we typically use it.
Whenever the layout or template of a particular page changes, you'd need to re-run the task on that template to extract its critical styles. If you have a page that frequently uses different designs, you'd need to run the task whenever one of the new designs is deployed.
Hope that helps!
Thanks for the reply. That makes perfect sense.
I'm curious if you've tried using Google's PageSpeed module for handling inlining JS/CSS and if it works better/worse than something like criticalCSS?
I haven’t used it personally, no. But I think it does have a similar feature. Not sure how it’s handled
On Jul 13, 2015, at 4:05 PM, Matt Messinger notifications@github.com wrote:
Thanks for the reply. That makes perfect sense.
I'm curious if you've tried using Google's PageSpeed module for handling inlining JS/CSS and if it works better/worse than something like criticalCSS?
—
Reply to this email directly or view it on GitHub #34 (comment).
Fair enough. Thanks again, Scott!
P.S. Just bought your new book--really looking forward to diving in.
Thanks so much! I hope you find it useful :)
On Jul 13, 2015, at 4:07 PM, Matt Messinger notifications@github.com wrote:
Fair enough. Thanks again, Scott!
P.S. Just bought your new book--really looking forward to diving in.
—
Reply to this email directly or view it on GitHub #34 (comment).