21 Responses

  1. Paul Paul December 6, 2009 at 11:29 am |

    After a quick look at the template hierachy above, I have a feeling that it should become wordpress standard soon.

    The template hierachy that wordpress currently uses is very difficult to fit in most of the custom project, it’s like we have to dig in and mess with conditional loop everytime.

    So I hope hybrid’s system will simplify the process here.

  2. Patrick Daly Patrick Daly December 6, 2009 at 12:40 pm |

    I definitely agree that the default templating system could use some reworking. For the most part it hasn’t changed since the beginning (when the vision for WordPress only including blogging). Now that WP has expanded as much as it has the structure of the system as well as the naming conventions should reflect that of a much more flexible CMS.

    For now, I can’t think of any more ways to improve upon your design.

  3. Robert Robert December 8, 2009 at 3:59 pm |

    This is definitely a step in a good direction. I’m working on projects that will require exactly this sort of templating capability as there will be different post types and archive requirements.

    I don’t see the category in your diagram so I’ll assume there is no change to that approach.

    I reckon that taxonomies will play an important role so any enhancements around the way we can display them and especially filter data using taxonomies will be very useful.

  4. designOdyssey designOdyssey December 9, 2009 at 2:01 am |

    Don’t quite understand it all yet (category and taxonomy interchangeability), but being able to use post and page templates this way will help me. I have at least two post types in my project other than traditional posts. Great work.

  5. Ed Nailor Ed Nailor December 11, 2009 at 11:15 pm |

    Just getting started with Hybrid, and from what I have seen I am blown away. My question, just getting started, is will this make any major changes to a current setup when you upgrade to 0.7 upon final release? I don’t want to go through learning how to customize my new hybrid theme (plan to use hybrid-news) just to have to relearn things again.

  6. watsontcbc watsontcbc December 14, 2009 at 7:45 pm |


    I am learning CSS, WordPress and ThemeHybrid, while I am building a somewhat complex e-commerce site. This sounds like just what I need.

    I also have same question as Ed – don’t want to have to learn and build this twice.

    Thanks for the great system you’ve developed.


  7. watsontcbc watsontcbc December 15, 2009 at 12:30 pm |

    Thanks Justin – glad to know it won’t be a problem. But I’m confused about this statement:
    “everything else is new or doesn’t really apply to child theme developers as much as it would be to folks that are eager to use the upcoming framework in their own themes.”
    Please pardon my novice ignorance, but I thought Hybrid was already basically a framework that you are, in a sense, just formalizing with Hybrid .7, right? Or am I misunderstanding (wouldn’t surprise me) your post on “What’s in store for Hybrid 0.7?” http://themehybrid.com/archives/2009/11/whats-in-store-for-hybrid-0-7

    The reason for this sort of question is to determine the best way to use what you have provided. My desire (and current work, actually) is to build sites based on your excellent Hybrid foundation that are a unique presentation specifically for my businesses and clients. I would like to understand if I should be using Hybrid alone or with Skeleton to create child themes, or use the framework. I have looked at other frameworks, and believe your approach to be the most solid and well-considered – the safest and most stable one to use.

    Thanks for your help!


  8. rickybuchanan rickybuchanan December 19, 2009 at 10:02 pm |

    The page/post/attachment-template.php ones confuse me – they seem to override the more specific ones we could use for a post (with the slug, ID, etc.) but I’m not sure why?

    Other than that, it looks fantastically adaptable!


  9. Hybrid version 0.7 theme release Hybrid version 0.7 theme release December 29, 2009 at 4:35 am |

    [...] previously written about the changes in the template hierarchy, so I’m not going into detail here. It should make creating custom templates much easier and [...]

  10. Samuel Samuel January 13, 2010 at 7:36 am |

    By the way Justin, Why don’t you like nested comments? By default none of your themes support nested comments. Hope you can add that feature next time without adding any additional code by end-user.

Comments are closed.