<div dir="ltr"><div>OT - Although I agree with Otto to a certain extent in finding a consistency in that naming convention, I cannot help but think the "standard-ish"-ness of the use of "content" may be driven more by copy and paste techniques than an informed decision to use "content" as a template name root.That being the case, I chose to use the theme slug as the template root and consider it in equal standing as "content", "loop", or any other "common" word/phrase ... and the idea of refactoring all of my themes to use "content" just doesn't appeal to me (*grin*).<br>
</div></div><div class="gmail_extra"><br clear="all"><div>Edward Caissie<br>aka Cais.</div>
<br><br><div class="gmail_quote">On Sat, Feb 2, 2013 at 6:38 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.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">On Sat, Feb 2, 2013 at 5:15 PM, Bruce Wampler <<a href="mailto:weavertheme@gmail.com">weavertheme@gmail.com</a>> wrote:<br>
> Given that the templates are supposed to be loaded using get_template_part<br>
> anyway, maybe the functionality belongs there and no one would have to do<br>
> anything.<br>
><br>
> Bruce Wampler<br>
><br>
<br>
</div>It would be nice if there was a sort of standardized "list" of template parts.<br>
<br>
For example, "content" is starting to be standard-ish. Jetpack<br>
specifically uses it in the Infinite-Scroll implementation.<br>
<br>
For the definition of it, I'd make it something along these lines:<br>
<br>
= Template Part Standard =<br>
<br>
Primary name: "content"<br>
<br>
Secondary name: post format (from get_post_format)<br>
<br>
Description: The content template part is the entirety of the post<br>
output that is inside "the Loop". This would be the main "div" or<br>
other container that gets the post_class() call added to it for the<br>
post classes, as well as everything inside it. Note that by moving<br>
this content into a template part, the context of the executing code<br>
would no longer be global, so commonly used variables like $post and<br>
similar would need to be declared as explicitly global at the<br>
beginning of the template part file for them to accessible.<br>
<br>
Example usage: In the Loop.<br>
<br>
while (have_posts()) : the_post();<br>
get_template_part( 'content', get_post_format() );<br>
endwhile;<br>
<br>
Uses: The use of the content template part enables the content of a<br>
post to be generated from a separate file as well as by other plugins<br>
or code. So, for example, Jetpack's Infinite Scroll feature is capable<br>
of using the content part to generate the post content individually,<br>
allowing the posts to be sent to the page via javascript requests,<br>
thus enabling the infinite-scroll behavior. This method also allows<br>
for easy customization of the individual look of posts using various<br>
post formats, since content.php can be separated from<br>
content-quote.php or content-aside.php, for example.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Otto<br>
</font></span><div class="HOEnZb"><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>