Themes intended for general, public distribution shouldn't be *implementing* Custom Post Types, IMHO. Custom Post Types create content, and content should maintain portability among Themes, and there is simply no good way to ensure that Theme-to-Theme naming of CPTs will be consistent.<div>
<br></div><div>I like the idea of support for "Supported Plugins", and any functional implementation that could be built around it. That's probably a very long-term goal, though.</div><div><br></div><div>Chip<br>
<br><div class="gmail_quote">On Mon, May 2, 2011 at 10:20 AM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
</div>Chip:<br>
What about Custom Post Types? If your theme implements any CPT<br>
functionality, it steps directly on that bright line.<br>
<div class="im"><br>
</div>There ought to be a method for some sort of "Supports Plugins:" header<br>
tags for themes so that, as a theme installation step, an end user<br>
could specify "Download and activate all plugins marked as 'supported'<br>
in this current theme."<br>
<font color="#888888"><br>
<br>
--<br>
-Doug<br>
@zamoose<br>
<a href="http://literalbarrage.org/blog/" target="_blank">http://literalbarrage.org/blog/</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>