<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Thanks, Danny. Lots of great-to-know things here!</div></div><div><br></div><div>Jeff</div><div><br>On Mar 3, 2013, at 12:43 PM, Danny Englander <<a href="mailto:highrockmedia@gmail.com">highrockmedia@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>Hi Jeff, <div><br></div><div>The custom node template should have two dashes after "node". So for example if your content type is called "Product Type" and the machine name is "product_type", then the node template would be "node--product_type.tpl.php". Note the double dash after node and then the underscore for the content type machine name. This is a change for Drupal 7 as in Drupal 6, it was "node-" with one dash. <div><br></div><div>That being said, you can also change the entire layout contextually for Omega by using <i>Delta + Context</i>. This powerful combo gives you the ability to change your Omega sub-theme layout based on a context such as content type, path etc… So now with your Delta theme variation, you can move zones around or whatever you want. It's pretty powerful and amazing. </div><div><br></div><div>I'd say the difference between using a custom node template and Delta + context is if you have specific fields that you want to theme that are unique to a content type, then use a custom node template or even Display Suite for that matter. If you want to entirely change regions and zones for a content type, i.e., change the page layout, then perhaps use Delta + Context. </div><div><br></div><div>A use case for Delta + Context then would be if you completely want to change the page layout for your home page. Omega 3.x does not use page.tpl.php or a variation thereof so in this case you would want to create a Delta template for <i><front></i> and then use a context for that. </div><div><br></div><div>Reference:</div><div><br></div><div><a href="http://drupal.org/project/delta">http://drupal.org/project/delta</a></div><div><a href="http://drupal.org/project/context">http://drupal.org/project/context</a></div><div><a href="http://drupal.org/project/ds">http://drupal.org/project/ds</a></div><div><br></div><div>I think there are some tutorials for this out there as well for Delta + Context. </div><div><br></div><div>-- Danny<br><div><br></div><div><br></div><div><br></div></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>themes mailing list</span><br><span><a href="mailto:themes@drupal.org">themes@drupal.org</a></span><br><span><a href="http://lists.drupal.org/mailman/listinfo/themes">http://lists.drupal.org/mailman/listinfo/themes</a></span><br></div></blockquote></body></html>