Advice for using Exhale, Composer and Git (+WooCommerce)

2 Replies ·

  1. Hi Justin.
    I’ve just ‘upgraded’ my workflow to include a VCS (Git + GitHub) and have chosen Exhale as an up-to-date WordPress ‘framework’ to go forward with. I had intended to use [Mythic?] – but Exhale is apparently now the most efficient / mobile-friendly way ahead if using Hybrid Core?

    Quick background – I’ve been coding websites in PHP/Javascript/CSS etc for over a decade, started using WordPress around v3.0, found YOU and your excellent articles on WP CPTs (that helped convince me WP was the way to go) and started using Hybrid Core 1.5. I currently have a site still using HC 3.0 that I hope to update soon.

    My current task is to update a site from a previous dev’s creation that used the ‘dreaded’ Visual Composer. I’m hoping to convert this using Exhale as the parent theme and my mods in the child. I’m not so familiar with using Composer, though I seem to have got it working on my local server, so was wondering if you have any pointers to any helpful articles?

    Thanks for all that you do, Justin – you’re a star! 🙂

  2. Justin Tadlock

    I would not call Exhale anything like a framework. It’s a theme primarily meant for end users. If you’re looking at it as something as a development tool, it’s not going to be ideal for that.

    It can be OK as a parent theme if your child themes stick pretty closely to just style.css mods and overwriting the /config files. See the available Mountains, Unravel, or Manuscript child themes as examples.

    I’m constantly working on it and changing things that will absolutely break heavy child theme modifications upon updates. It’s still a really young project, and I haven’t devoted a lot of time to making it as child-theme-friendly as I’d like. However, I do have plans in that regard, which will likely happen in 2020 as some of the features I’m building have been worked out.

    I do think it can do well for client work where you want to get something set up quick and change fonts, colors, and other stylistic features while leaving most of the custom stuff to the block editor (Gutenberg).

    It can also be something worth forking into your own parent theme if that’s something you’re interested in.

    You don’t need Composer or anything like to work with Exhale. It’s available as a standard ZIP file for production. And, it’s probably not the ideal intro to some of those tools because quite a bit of it is customized to my personal liking, and I’m not above changing it on a whim (it’s based off Mythic though).


    Mythic is what you want if you want a starting point for working with Hybrid Core. We have both #advanced and #mythic Slack channels (you should have an invite) where we dive into discussions on it.

    There are step-by-step instructions on installing Mythic via Composer: https://github.com/justintadlock/mythic/wiki/Installation

    As for learning Composer, honestly, I just done a lot of trial and error until things made sense. But, Rarst does have a site devoted to using Composer with WP: https://composer.rarst.net/

  3. renWeb

    Excellent – thanks for the clarification, Justin. Back to ‘plan A’ then 🙂