WordPress Plugins and Themes

13 Comments

  1. wiselywoven

    I’m excited about your renewed vision Justin. Looking forward to what unfolds.

  2. Emyr Thomas

    I like your vision, and your careful definition of what a child theme should be. I’m excited to see the new ‘boxes” (a.k.a. parent themes) you have in store. Will we possibly see themes that are built to support third party plugins, for example an eCommerce theme, or an Event Calendar theme in the future?

  3. hayley

    Makes perfect sense, I’m looking forward to seeing the box range grow. Might I ask what Box number is for?

  4. […] child themes would in my opinion be to restrict developers to just “paint the box” as Justin Tadlock explains about his latest parent theme […]

  5. iVideoWeb

    Hi Justin,
    Its a good thinking, but I don’t agree with your parent child theme ideology (to its full extent), I am thinking the reason for this approach (from yo) is so you can quickly grow your Core Framework without worrying about backwards compatibility, or worrying about breaking any child themes, but I believe providing more boxes means you are more bound, you will have to be extra careful for you parent themes (boxes), as you will know now the responsibility is 100% on you, and its not gonna restrict people still from adding functionality to child themes etc (instead of just working with css / colors etc).

    Instead your Hybrid Framework is a unique framework which allows us (dev’s) to just plug and play functionality using extensions system, which you should focus on by providing more useful extensions such as (restaurant related, ecommerce related, membership related and so on), so in child themes we can just enable disable those extensions based on our project needs, and you can’t provide themes for every scenario or every website need, its better known or understood by the developer building the website, and responsibility lies on them not you.

    One of the main reasons I am using your Hybrid Core framework is its extension system, as it not only allow me to use existing extensions instead I can build my own and use the same logic for my own extensions and in child theme just enable / disable them according to project needs.

    Its just my own ideology, and I am sure everybody have their own point of view about parent / child themes etc.

    But as I know (most of you will agree with me), every theme has about 80% same features, functionality, requirements on every new project / website, so its kind of redundent effort from my point of view, that’s the reason we opt for parent / child themes approach.

    Just my two cents suggestion,

    Thanks,
    Syed

    • Justin Tadlock

      I think you may have misunderstood what this post was about, so I’ll try to clear up some of it in my reply.

      Nothing is really changing at Theme Hybrid on the development side of things. Hybrid Core will still work the same way. Parent theme development will work the same way. This is not some new philosophy that I just came up with. It’s been the standing philosophy since 2010.

      The major difference is that there’s going to be a shift in focus from developers to users. I’ve spent the last few years building up a great set of tools for developers (and will continue doing so), but it’s time to put the focus back on regular end users.

      It’s only now that I feel like the tools I’ve built and WordPress core has matured enough to fully see my original vision through. It’s only now that I’ve decided to share more details of this vision with others.

      I am thinking the reason for this approach (from yo) is so you can quickly grow your Core Framework without worrying about backwards compatibility, or worrying about breaking any child themes,

      This has nothing to do with my framework. The framework is merely a development tool for myself and other developers.

      I am, however, wanting to more quickly grow the library of themes and make more design options available to normal users, paticularly those users who don’t care anything about frameworks, PHP, etc. They just want a theme that works. That is the target audience of this new theme as well as the themes I have in mind for the future.

      but I believe providing more boxes means you are more bound, you will have to be extra careful for you parent themes (boxes), as you will know now the responsibility is 100% on you,

      This is no different than what I’ve been doing for the past few years.

      and its not gonna restrict people still from adding functionality to child themes etc (instead of just working with css / colors etc).

      It’s not meant to restrict people from adding functionality to child themes. I actively encouarge people to do this.

      The only people it restricts are me and other people who want to add public child themes to the ThemeHybrid.com as part of the theme collection. That’s something I do have full control over.

      which you should focus on by providing more useful extensions such as (restaurant related, ecommerce related, membership related and so on),

      I plan to continue adding useful extensions and features to the framework. That’s not going to change.

      As for the specific extension ideas listed, I’m about 99% sure those will never happen (restaurant, e-commerce, membership). I consider those outside the scope of what the framework is meant to accomplish.

      so in child themes we can just enable disable those extensions based on our project needs,

      Extensions really aren’t meant to be enabled/disabled via child themes. Nevertheless, people are always free to do what they want on their own site and build their own system however they want. That’s not my concern anyway.

  6. Jason DAvis

    Justin, I can’t wait to get my hands on / play with / your box. Just couldn’t help myself.

    Cheers to you though – totally clear vision and I’ve got nothing but respect for it.

    JD

  7. iVideoWeb

    Thanks for clearing my confusion. I think you were just thinking out loud this time otherwise its been your standpoint since last few years, that’s more comforting as I have found your contributions and plans to meet my needs and liking.

    Thanks for the wonderful work you have been doing and will keep doing what you do best. 😉

  8. […] child themes would in my opinion be to restrict developers to just “paint the box” as Justin Tadlock explains about his latest parent theme […]

  9. Dr. John Lee

    Thank you so much!

  10. Natali

    Good evening!

    I has installed theme Unicum and I have some questions, including child theme, but I can not ask them. On http://wordpress.org/support/theme/unique you can not answer the questions. Do you have support free or it only for money?

    If only for the money, then maybe we can help each other mutually? I can be translated into Russian, and you help me to configure it.

    PS. I’m sorry, I do not speak English, use Google translator online, so there may be problems with understanding.

Comments are closed.