Trevor Green

Adds a custom post type of css that will compile all entries into a single minified css file that will automatically be enqueued to your site.
Minified CSS is stored in a transient for caching.
User now needs ‘edit_themes’ permission to see the css editor. By default this is only the administrator.
<h4>Shortcodes</h4>
Shortcodes are now processed during compilation of your css.
An new shortcode has been added called:
[meta key=”(name of arbitrary custom field)” post_id=”(optional)”]
This allows you to define a whatever custom fields you like on an individual css post and use them in your css.
Ex. a { color: [meta key=”my_color”]; }
So you can define common elements and use them throughout your css.
If you like you can use the option post_id to put those values from another post. So you can have one master css post with your primary colors and such and referance it in other posts.
<h4>Credits</h4>
Minification code from <a href="http://www.lateralcode.com/css-minifier/" rel="nofollow ugc">http://www.lateralcode.com/css-minifier/</a>
<h4>Notes on Function</h4>
All css is compiled on save unless the transient has expired. If which case a query is run to compile the css durning rendering. 
I may add option to use either a wp_option or a transient based upon user preferance.
Css is compiled by menu_order. I would like to add more options for better sorting.
There is an options page that outputs the css into a textarea so that you can review the final css in the dashboard.
Email me to request customizations <a href="mailto:trevor@mailagc.com" rel="nofollow ugc">trevor@mailagc.com</a>
Future options may also include the ability to write your css to your theme directory. This plugin currently must be active to keep the css available.
I’m trying to follow the path of Mark Jaquith. Read more here. 
<a href="http://markjaquith.wordpress.com/2011/06/07/how-to-write-a-plugin-that-ill-use/" rel="nofollow ugc">How to Write a Plugin I’ll use</a>
<a href="http://www.azuregreencreative.com" rel="nofollow ugc"></a>

COP CSS Custom Post Type Lite

Adds a custom post type for implementing theme independent css.

Seth Alling

Up until recently, WordPress gave two options: You could either disable comments and trackbacks by default for all pages and posts, or you could have them active by default. In WordPress version 4.3, this finally changed so comments are always disabled on new pages.
While the new change makes it easier for many of the sites, it make it harder for people who need to get the reverse and enable comments on all pages, or if they need to change the default for a custom post type. This plugin allows you to choose whether comments are enabled or disabled by default on all new posts, pages and custom post types, while still giving the ability to individually enable comments on posts or pages.
Also, this plugin provides a way to quickly disable all comments or pingbacks for a specific custom post type. It directly interacts with your database to modify the status, so it is highly recommended that you backup your database first. There shouldn’t be any issues using this feature, but it’s always good to play it safe.
<a href="https://github.com/sethta/no-page-comment" title="No Page Comment Development on Github" rel="nofollow ugc">View No Page Comment Development on Github</a>
<a href="https://github.com/sethta/no-page-comment/issues" title="Report an Issue about No Page Comment on Github" rel="nofollow ugc">Please Report any Issues about No Page Comment on Github</a>
<a href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=5WWP2EDSCAJR4" title="Donate to support the No Page Comment Plugin development" rel="nofollow ugc">Donate to Support No Page Comment Development</a>

No Page Comment

An admin interface to control the default comment and trackback settings on new posts, pages and custom post types.

COP CSS Custom Post Type Lite vs No Page Comment