6 Responses

  1. Victor
    Victor Published |

    I’m being studying PHP and WordPress (among other things), and now I’m digging into the WP Theme frameworks. Your post brings solid arguments to take into account when comparing “frameworks” and ThemeHybrid. I’ve been reading the code and documentation from one of those popular theme frameworks and themehybrid, and all I can say is …I’m all to ThemeHybrid.
    As I’m new in the WP coding arena and still learning…hope to be more active in a near future, my brain is still “digesting” Hooks (actions, filters), theme herarchy and so on :)
    And I’d also like to say, thank you, Justin!

    Reply
  2. haluk karamete
    haluk karamete Published |

    Justin,

    To help clarify some confusions, why not also get into the difference(s) between your framework and a good-old functions library?

    You’ve mentioned above that “I created a framework that mostly consists of standalone scripts that you can pick and choose to use… ”
    Is this something like a functions library?

    include ("justins_functions_1.php")
    include ("justins_functions_2.php") 

    and now the coder is on his own to tap in those functions?

    On a different note, it may also help comparing your framework to start themes, like underscore s? This is from their web page “Hi. I’m a starter theme called _s, or underscores, if you like. I’m a theme meant for hacking so don’t use me as a Parent Theme.”

    Close? Then, I’d say a little more clarifications needed in this article.

    Perhaps, you may do something like this;
    Assume one is going with one of the possible of 3 different routes you offer here,
    which are;

    * Hybrid-Core
    * Hybrid
    * Hybrid Base

    What would be the major mile-stones he needs to go through to end up with a theme that would make it to wordpress.org repository?

    Why would one pick one over the other?

    Reply
  3. haluk karamete
    haluk karamete Published |

    Justin, thank you for your reply for my previous question.

    Now, this one deals with a different angle.

    Having some guidance on following process in creating themes?

    Do you have some docs that explains the process you follow when starting with a new theme, that is based on hybrid-core?

    Do you use an empty boiler plate approach -where you have a theme folder that’s got the common WordPress theme files in it ( such as header, index, archive etc) ) which are empty & waiting for you to fill-in?

    Before answering this, let me drive this home so you see where I’m trying to get at.

    Let’s say I want to build a new theme called “hybrid-twitter-bootstrap”.

    What route would I take so that your code meets their mark up/css and both live happily together?

    Basically, the end result is powered by your hybrid-core, but the generated html becomes those of http://getbootstrap.com/2.3.2/getting-started.html#examples – where the entire markup, css & responsiveness are driven by bootstrap.

    Is it even recommendable to go down that route? You may say, for example, if you are using my framework, why would you go seek the responsiveness and CSS and markup somewhere else and that defeats the purpose..

    I feel that there are people out there who are still having a hard-time in answering questions like this, that is how to bring the best of both worlds ( solid WP coding skills that people like yourself bring to the table and a stunning front-end which is reported to be the most popular project on github.
    source: http://en.wikipedia.org/wiki/Twitter_Bootstrap

    So what route would you take if you were to build that hybrid-twitter-bootstrap theme?

    Reply
  4. Jame
    Jame Published |

    Whenever I read your argument about WordPress, it’s very reasonable and very true. Therefore, your work, Hybrid Framework, will definitely perform great including best practice, security and as well as the support, Private Support Forum.

    That’s great to use Hybrid Framework, but now having more and more issue in mind. I guest I should join the support forum from now on.

    Reply

Leave a Reply

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/Web site in attribution.

Please use your real name or a pseudonym (i.e., pen name, alias, nom de plume) when commenting. If you add your site name, company name, or something completely random, I'll likely change it to whatever I want.

css.php