Mak, will you continue to create "Frames" in addition to "Components"? Or will "Frames" become "Components"?
Mak . I'm a little confused about something. Previously you were creating "Frames". Now you're creating "Components". I'm curious if you'll be continuing to develop and create lots and lots of frames .. OR .. will you stop creating frames, and instead focus on Components? (I'm thinking you'll drop frames and turn this into Components. Is that correct?) Please explain what you plan to do with these two features in KrafterPro. Thanks, Gary
That's not correct. Frames and are going to be built in parallel and are 2 different products. Frames = Pre-designed section, Components = pre-designed modules and rows.
Mak . Mak, I'm confused because it's my understanding that we can use Divi Components to create "Reusable modules, rows, and sections that stay in sync across an entire website. The idea is to build an element once (module, row and sections), save it as a component, and you can then use it on as many pages as you like. When you edit the component, every copy of it updates" UNLESS your disconnect certain elements from a global component so they won't replicate as a duplicate item in every instance .. everywhere.
Therefore, the new Divi Components can do everything that your prior creation of Frames did. That's why I was asking. Since you can create everything that you created when using Frames .. as a Divi Component, I didn't think you'd be wanting to develop and have to maintain two features that basically did the same thing.
So, being that your prior development of Frames as well as Divi's new development of Components can "BOTH" create reusable Sections as well as Groups, Rows, and Modules, I just thought it would make sense to merge your idea of Frames into the new Divi Components.
Can you explain why you're still thinking about keeping Frames, since the new Divi Components can do the same thing?
Thanks,
Gary
@stepaheadweb Hi Gary, great question, and you’re right that a Component can hold a whole section. The difference isn’t what each one can hold, it’s how they behave once they’re on the page. Components and Frames do two different jobs, and they work best together.
1. Components are meant to stay in sync. Sections usually shouldn’t.
Syncing is the whole point of a Component. Edit it once and every copy updates. That’s perfect for a pricing card, a CTA, a notice, or a button group that should look the same everywhere. But a section is a starting point you customise per page: different heading, different image, different number of cards. If you save a section as a Component, you have two options. You can keep it synced, and then editing it on one page changes it everywhere. Or you can detach it, and then it’s no longer a Component. Either way you’re fighting the feature.
2. Granularity.
If a section is one big Component, the card inside it is locked into that section. To reuse or edit that card by itself, you have to detach the section first. Keeping Components small (cards, CTAs, notices) means they stay reusable anywhere, and sections stay flexible.
3. Frames adapt to your site’s design system.
A Frame isn’t saved to one site’s library. When you insert it, it takes on your site’s colours, fonts, spacing, and presets through KrafterPRO. The same Frame looks native on every site you build. That’s the part Components weren’t designed to do.
4. The AI workflow needs both layers.
For AI-assisted building, Components are the vocabulary: the cards, buttons, and CTAs. Frames are the proven layout patterns. The AI assembles unique pages by combining the two, instead of copying the same synced section onto every page.
Short version: Components are the bricks. Frames are the blueprints. Use Components for things that should stay identical everywhere, and Frames for layouts you want to start from and make your own.
@funnelstoincome Okay. Got it. Thanks. I appreciated your explanation.