The Fusion sub-agent for Publish is a built-in AI agent that understands how to work with the Publish CMS. It removes the need for manual configuration, bespoke engineering scripts, or CMS-specific domain knowledge.
Anyone with access to Fusion can direct it using plain language, and it handles the technical work.
The sub-agent can do three things:
- Install the Publish SDK into an existing web app.
- Migrate components, tokens, and branding to be compatible with Publish CMS.
- Build new components that are registered and configurable within Publish.
Use the Fusion sub-agent any time the work involves setting up or extending Publish at a code level. For example:
- "Set up Publish in my Next.js app."
- "Migrate my existing site so it works with Publish."
- "Build a new hero banner component and make it available in Publish."
- "Register this component with Publish and make the headline and CTA configurable."
- "Map my existing components to Publish content models."
Before using the Fusion sub-agent, confirm the following:
- Both Fusion and Publish products are active on your Builder account.
- Publish is set up and configured. Content models, entries, and the component registry are ready. For more details, visit Get started with Publish.
- Fusion is connected to your web app's repository. For more details, visit Get started with Projects.
The sub-agent comes pre-built with Fusion and requires no additional configuration to work with your Publish CMS.
Use this when you have an existing web app connected to Fusion and want to add Publish as the content management layer.
The sub-agent scaffolds the integration, wires up the component registry, and connects your content models. No manual setup is required.
Open a new branch in Fusion and tell the sub-agent to install the Publish SDK into your app. For more details, visit Create and duplicate branches.
You don't need to specify your framework or existing setup, as Fusion already knows.
If you have existing content models or component patterns you want the sub-agent to follow, mention them here. It will use them as a reference during setup.
The sub-agent sets up the Publish SDK, wires the component registry, and connects your existing components where possible. Review the changes on the branch before merging.
For more details on how to create a pull request from Fusion, visit Create a pull request.
Once the branch is merged and deployed, confirm that your components appear correctly in the Publish visual editor and that content models are mapped as expected.
For more details on Publish, visit:
Submit a PR from Fusion through your normal review and deploy process. Once deployed, your app is live with Publish as the content management layer.
Use this when you have an existing site, such as a site built on another CMS, and want to migrate it to be compatible with Publish. The sub-agent maps your existing components and content models to the Publish structure and handles the re-wiring.
Open a new branch in Fusion and tell the sub-agent to migrate your existing setup to Publish. For more details, visit Create and duplicate branches.
The sub-agent produces a mapping of your existing components and content models to their Publish equivalents. Review this before proceeding. If something is wrong, share the issue with Fusion.
The subagent can also register your app styles as Builder Design Tokens that are then used in the Publish Visual Editor. This is an optional step, but can help to ensure that content created in Publish matches your app’s styles.
With the migration branch active, open the Publish visual editor and confirm that components render correctly and content models are mapped as expected. Iterate in Fusion if adjustments are needed.
For more details on Publish, visit:
Submit a PR from Fusion through your normal review and deploy process. Once deployed, your app is live with Publish as the content management layer.
Use this when you need a new component that doesn't exist yet — or when an existing component needs to be updated and made available in Publish. This is the same capability used in the Fusion Preview for Publish workflow.
For example:
- "Build me a new product wizard component."
- "Update this existing banner to include a fade-in animation."
- "Create a new mega menu with product categories and hover states."
- "Build a carousel that swipes differently on mobile."
The sub-agent builds the component, registers it with the Publish component registry, and surfaces the properties you specify as configurable fields in the visual editor. No manual registration required.
For more details, visit Fusion Preview for Publish.