Screencast Tuesday: What's Coming in Headway 3.0.5

I thought this week I’d spend some time showing you what’s coming in Headway 3.0.5. It’s on track for being released this week or early next week. That said, I thought I’d show you two of my favorite features along with some enhancements to the content block. Hope you all enjoy!! πŸ™‚

Spread the word!

31 Responses

  1. 3.0.5 already, wow.

    Wizard looks good nice to see a few presets.

    A site in half a minute!

    Responsive grid – looks good for mobile devices.

    But there’s more – hide menu.

    This is a great selling feature.

    Content block changes – great to have the options.

    Love the video AJ and Headway just keeps getting better and better.

    • @wmwebdes I really like the work Clay’s done with the Responsive Grid feature. I’m not a big fan of responsive stuff just yet, but from people I’ve talked to, this really aims at making it pretty easy for people to get something decent looking on a lot of devices out there. I think the real power will come with child themes and theme designers. πŸ™‚ They might be able to convince me to build some sort of a responsive site (or clients will!).

      • @AJMorris

        Yep, more and more people just take out their mobile and surf for info.

        I’ve noticed from my Google Analytics that the percentage of mobile browsers is slowly increasing.

  2. Great Screencast again ajmorris and some really nice additions to Headway 3.0.5. Looking forward to playing with the responsive side of things.

    • @Jeffsarge

      Hey Jeff,

      You can always add in additional responsive CSS rules by adding an additional stylesheet and putting media queries in that. This method would add your responsive rules to the existing Headway rules (which I would recommend).

      Or, you can create a child theme and disable the Headway responsive grid by using remove_theme_support(‘headway-responsive-grid’). Then, add in your own completely custom responsive CSS.

      If you want to make very small changes to the Headway responsive CSS, you can use the ‘headway_responsive_grid_css’ filter to manipulate it directly with PHP.

  3. Having preset layouts will be a big help for people, glad to see that’s in there. Also liking the new changes to the Content Block. Now I can redesign my own site on 3 and it will look amazing. πŸ™‚

  4. Great video! I am so happy to see that there is now an option to turn off the comments on the custom query option. That was a concern on a client site that I have been in the middle of building.

    One thing I would love to see is an easy way to adjust padding for each individual block without having to use custom code. Will that be an option in the future as well?

    DAWN

  5. I’ve noticed my site (which is currently built on 2.13 (or the old one)) does not “scale” well when I try to view the content column on my blackberry browswer. Most other WP sites allow me to “zoom” to my column and changes the text so its readable and I don’t have to scroll.

    Does 3.0 fix that problem or is there a setting I need to tweak in WP/Headway?

    Thanks!

    Ryan

    http://www.weddingphotographygig.com

    • @Ryan Oakley

      The responsiveness in 3.0.5 should help out with this, but I’ve never heard of that being an issue with Headway 2.0.

      I know all Headway 2.0 websites looked perfectly fine on iPhone and Android browsers. I can’t think of any specific reasons why they wouldn’t scale correctly on BlackBerry’s browser.

  6. Hi, guys! You are really doing it! Thanks for the responsive features, Clay! Waiting to try out 3.0.5.
    Milena BΓΆhm,
    I DESIGN STUDIO

  7. Any chance of making the intro music a bit quieter? Nearly had a heart attack. Then I instantly had to turn down my sound and then AJ’s voice was too soft. Heart is still pounding. The other is issue is that I can only control the volume when viewing the screen in smaller format. If I switch to full screen, then I lose volume and the video reverts to the beginning and I have to survive the intro music— again! Now I will watch the video and hopefully not have any more shocks for the day πŸ™‚

  8. YO and WooT! Responsive Grid! I have been trying to design for the mobile market by putting stuff on the left first… This is *killer*. Thank you!

    Have you considered releasing point.point releases as trials to developers before launch? You are packing so much into point.point a play mode would help!

    • @robynski The Headway 2.0 to 3.0 upgrade mechanism will not be available until the first batch of child themes is available.

      Please understand, Headway 3.0 is a completely different product and a complete rewrite over Headway 2.0. It’s not as simple as transferring settings from point A to point B. There will be a ton of math and other wizardry involved :-).

      • @claygriffiths@robynski You should at least continue to support 2.0 for those who are not able to re-do their sites. That is what is upsetting to me. I was told that February is when you will stop supporting it. Definitely not fair to those of my clients who I built sites for recently using 2.0 and they will not be able to afford to have their sites completely re-built using 3.0.

        • @paintermommy

          If the upgrade mechanism that handles upgrades from 2.0 to 3.0 isn’t available by February 1st then we will extend the support period.

          Please note: we will NOT drop support for 2.0 until the upgrade mechanism is released.

      • @claygriffiths@robynski Yeah that’s not a great answer to me. To have to redo everything from scratch is far from easy from this end too. A bit of warning in advance would have been at least a courtesy for all of the non-coders using the platform.

        • @robynski@claygriffiths So then my clients currently on the 2.0 platform can upgrade to 3.0 without having to re-create their site designs? Is that what the upgrade will allow?

        • @paintermommy@robynski Yup. However, If you used custom CSS or hooks at any point, then that will have to be updated manually.

        • @robynski You are not going to have to redo anything from scratch when the upgrade mechanism is out.

          You can still use 2.0 in the meantime. We’re still supporting it along with 3.0.

  9. You should at least continue to support 2.0 for those who are not able to re-do their sites. That is what is upsetting to me. I was told that February is when you will stop supporting it. Definitely not fair to those of my clients who I built sites for recently using 2.0 and they will not be able to afford to have their sites completely re-built using 3.0.

Leave a reply

Copyright Β© 2016 Vesped Inc. All Rights Reserved. Proudly Powered by Headway and WordPress