16 Comments

  1. Justin Tadlock

    Now, we just need to get the ball rolling with some documentation in the wiki pages. It’s pretty sparse at the moment, but I’m sure we’ll get there in the coming months. I’ll be able to transfer some existing docs over. One of my big hopes is that this move frees me up to put more focus back on theme users, which make up for the bulk of Theme Hybrid’s user base.

    Thanks for the coverage, Jeff.

    Report

    • Ahmad Awais

      Looking forward to adopting Hybrid Core. Thanks a lot, Justin.

      Report

    • Anh Tran

      One question: can you explain why you dropped the Atomic hook functionality? I think it’s very useful in a theme framework. I’m using it in my theme and it’s very powerful.

      Report

      • Justin Tadlock

        That’s a legacy feature that I no longer use. I almost dropped it in 2.0 but kept it around for nostalgia. Some of these things go back to a time when child themes couldn’t even have templates. These were ideas we were playing around with back then. WordPress’ template part system really made this obsolete.

        Feel free to copy it from 2.0 if you need it. It’s not much code.

        Report

        • Anh Tran

          Thanks for your answer.

          Although the WordPress template system can solve this problem, for a theme which has many hooks (for plugins to hook into), I think it still useful. At least it reduces duplicated code and still keep the logic clear. But for simple themes, I agree with you. WordPress template parts are enough.

          Report

  2. John Teague

    I have to say that, after a long inspection of the 3.0 release, I am very impressed with Hybrid Core. Justin has done a wonderful job in creating a foundation that bridges the gap between those new to WordPress theming and seasoned theme developers who see the wisdom in not reinventing a perfected product. I look forward to building a new theme with Hybrid Core. And the community driven documentation is a smart move.

    Report

  3. Anh Tran

    Awesome! I’m happy that the documentation of Hybrid Core is public and shared on Github. Previously it was available for members of ThemeHybrid only.

    This is one of my favourite theme framework. Justin is doing a great work. Looking into the code of Hybrid Core is interesting and there is a lot of things to learn.

    Thanks Justin!

    Report

  4. Ciprian

    Great news! I’ve been eyeing the Stargazer theme for a while now, but the last update was a long time ago. Maybe this release will bring a theme update.

    Report

  5. Ryan Hellyer

    I have huge respect for the work that Justin does. It’s nice to see that the number of features is shrinking over time and instead of increasing. It’s too often that we see themes, plugins and other software expanding rapidly over time * glares at WordPress core*. It is rare to see anyone with the confidence to make things smaller and leaner.

    Report

  6. Blue

    Are you planning to add custom logo upload to customizer?

    Report

    • Justin Tadlock

      At the moment, I have no plans to add it, but I’ve given it some thought. Considering that the code would just basically be adding some custom text strings to core WP’s cropped image control, I’m not sure the control alone is worth it as a feature.

      If I ever did logos, I’d probably make a full feature where theme authors could make a simple add_theme_support() call (like custom header and background) along with custom functions for displaying the logo and such.

      Report

  7. Terence Milbourn

    Justin,

    I have searched and searched for a reliable, full featured, capable of heavy lifting Wiki plugin on the WordPress platform, and someone told me that Hybrid Core 3.0 might provide the answer?

    Any truth; now or in the future?

    Terence.

    Report

Comments are closed.

%d bloggers like this: