Skip to main content

Divi Community (FREE)

#Divi Related

The Future Of Divi 5 Design

In this video, I discuss how I think is the way we are going to be designing Websites with Divi 5

  • 9 likes
  • 4 comments

KC Pars

Krafter Pro sounds like a great idea, and I imagine it will solve some of the confusion that I’ve had every time I update or download either Krafter or Divi 5. It’s been hard to keep up.

I am about to design a few new sites. How long before Krafter Pro is available? If it’s not too long, I’ll probably wait to start these new sites.

Leo Woer

Mak,

this sounds amazing - I look forward to both Krafter pro, the templates and the updated training courses.

Until now I have absolutely enjoyed to be a lifetime member, and this will make it it even more exiting.

All the best

Leo

Thomas

Hello Mak, and thank you for your work.

This video does indeed clarify things, and I think Krafter Pro is an excellent idea.

However, I have a question that remains unanswered for now: I am currently building a website with Site Krafter Pro 7.5.1.

How compatible is it with your other products?

Thank you.

Pol Van Kerschaver

"Hi Mak,

The news about Crafter Pro is fantastic. As Divi 5 matures, having a dedicated design system is a game-changer. However, I have a major concern regarding the 'Update Workflow' and the 'Point of No Return' for new projects.

If I understand the logic correctly, there are two paths:

  1. The JSON/Preset path (Krafter): Fast to start, but leads to 'library clutter' and potential branding loss (fonts/colors) during updates.
  2. The Child Theme path (SiteKrafter): Clean, professional, and future-proof.

My biggest concern: Starting 'from scratch' the wrong way. If a user starts a project without your Child Theme foundation and builds the entire site using only JSON imports, they are effectively 'stuck'. If they want to switch to your improved system later, they basically have to rebuild the entire foundation. That's a 'point of no return' no professional wants to hit.

My reasoning for a Child Theme foundation in Crafter Pro: I want to use your expertise for the 'heavy lifting' (fluid logic, classes). By starting with a Child Theme, I can set my global branding—like switching your default Poppins to my Helvetica—in the database.

When you update the Child Theme files, my Helvetica and colors stay safe in the database, while the 'engine' (your logic) gets the upgrade. No clutter, no manual cleanup of 50 duplicated presets.

My question: Will Crafter Pro be a true 'Framework' that we must start with as a Child Theme to stay safe? Or will it remain a collection of JSON files that we keep importing?

I believe that for a professional, sustainable workflow, the 'Child Theme + Global Variables' approach is the only way to avoid being 'stuck' with a messy, unupdatable library later on.

Curious to hear your vision!"