I have several ‘types’ of content styles on my webiste. Specifically for ‘Posts’ I have some that are created with Thrive Architect, some that are built up from self-coded HTML code which are pretty big but done in the classic editor to minimize Thrive Bloat, and some normal type blog posts which are, more or less, simply text and images.
All of these ‘Posts’ are created in the usual Add New Post way.
In the Autoptimize Critical CSS tab I see the rules created for is_single, is_page, is_blog_page etc. All of the posts are listed under is_single. So I have Critical CSS creating one rule to cover all my three post ‘styles’.
I am aware of the ‘path’ option to create rules but afraid if creating rules for hundreds of pages and posts, then the size of the storage is going to become a problem. This is an assumption and perhaps you could comment on what problems I might face down the line ticking this option.
I wondered whether it would be a good idea to create a custom post type. Maybe 1 for Thrive Built Pages and another for Self-Coded pages without all the Thrive CSS which is not even used on those pages. Do you think this is a good idea and would bring benefits?
I assume a Custom Post Type would still be ‘is_single’ so if you think it is worthwhile, how do I ensure that a seperate rule is generated for that type automatically or do I need to do it manually if the critical.css service cannot handle it automatically.
Could you advise best practice here? Thank you so much in advance.
- The topic ‘Best Practice for Rules by Type’ is closed to new replies.