How to Convert a Canvas Literal Into a Resource
This guide shows you how to promote a literal node on a Canvas into a first-class Schema or Experience.
Prerequisites
- Canvas must be available in your Space. See How to Check Whether Canvas Is Available in a Space.
- You must be an admin of the Space. See Canvas Access.
- You need a literal node on the Canvas. Deriving one is covered in How to Get Content Onto a Canvas.
Steps
- Open the literal node's actions menu.
- Select Convert to resource.
- Select the destination folder, or leave it unset for the Space root.
- Confirm.
Result: On success, the literal node is replaced in place by a reference node pointing at the new resource, the Canvas gets a new version summarised Converted <type> literal <nodeId>, and you are offered the resource's editor at:
- Schema —
/spaces/<spaceId>/settings/schemas/<resourceId> - Experience —
/spaces/<spaceId>/settings/experiences/<resourceId>
Troubleshooting
Conversion Fails
Conversion is all-or-nothing. If it fails, no resource is created and the Canvas is not changed.
Message | Meaning |
|---|---|
| Someone else saved the Canvas while you were converting. Reload and retry. |
| The node has generated content that has not been accepted. |
| Rename the literal, or the existing resource, and retry. |
| The node points at an artifact this Space does not own. |
| The pinned artifact is not a valid definition of that type. |
| See above. Flow literals cannot be converted. |
Limitations
- Convert to resource is not offered on
flow:literalnodes. Flow literals cannot be converted. If a Flow conversion is attempted anyway, it fails withFlow conversion requires explicit confirmation. - After conversion, authoring authority moves to the dedicated editor. Editing the Canvas reference node does not edit the resource, and editing the resource does not change the Canvas.
- Conversion is idempotent per source node and definition artifact. Converting the same literal twice returns the same resource rather than creating a duplicate.