4 Comments

  1. Adam

    Seems to be a reoccurring patterns of businesses leaving Envato, I blame the lack of proper developers licensing.

    Report

  2. Luke Cavanagh

    Seems like building the theme functions and page builder is the way to go for being modular, Avada has the page builder as plugin in the upcoming version.

    Report

    • Jeff

      As a developer of a page builder theme that follows the same hybrid approach of Layers, I’d like to add my two cents opinion.
      Separating theme versus plugin functionality is a smart rule and there are many (also commercial btw) totally legit reasons to want this, but there’s definitely a trade off. In our experience, integrating the page builder (which initially, in private beta stage, actually WAS a plugin) and the Theme, allowed to keep a lighter footprint and guarantee that things work out of the box much better.

      As a silly example, knowing which grid CSS framework the Theme is based on, allows the Page Builder side to NOT have to load another one.

      Of course there are trade-offs with both approaches, but personally I was fed up seeing so many sites built piling plugins on plugins, resulting in inferior performance and great sluggyness.
      Some people rant about WordPress being slow, only because they run sites with such kind of “plugin-tower” approach – a “pervert” way to see software modularity.

      Report

      • Ron

        @Jeff….As an aside, I feel the need to comment on something.

        Your theme looks pretty cool. If I wasn’t using Divi I might consider it.

        You really need someone to proofread your entire site. It’s bad. Nothing that can’t be fixed easy enough. Just TONS of grammatical errors and plain bad copyrighting.

        Just a heads up….you have something good there and it would suck to have this cost you sales. :)

        Report

Comments are closed.

%d bloggers like this: