Developer Module Flows

This section explains how Craftive modules work together from a developer perspective. The goal is to make module flow and the content lifecycle easy to understand.

Main flow

A typical Craftive content flow works like this:

1. An editor prepares page or component content in the Admin workspace.
2. Page Builder defines the template and slot structure of the page.
3. Component Library provides the behavior model for content blocks added to slots.
4. Media Library manages the visual and file assets needed by components.
5. SmartEdit helps the editor preview and edit the page in its real context.
6. After the publish decision, public delivery exposes current content to storefronts or other frontend experiences.

Developer mental model

In Craftive, developers do not hardcode every page by hand. They build experiences that render a content model.

Useful questions:

• Which template should represent this page?
• Which slots does the template need?
• Which component types can be used in each slot?
• Does the component contain repeated entries?
• Should media be attached to the whole component or to individual entries?
• How will editors preview the change before publishing?

Safe integration principles

• Admin operations and public delivery behavior should be considered separately.
• Public frontends should only show content that is approved for publication.
• Editor preview behavior should not be mixed with live visitor behavior.
• Media, language, and publication state should be handled from the content contract, not frontend assumptions.
• Empty content, missing media, and unpublished language variations should have resilient UI states.