Choose between a self-contained full template and a component-based composite template.

Overview

Choose between a self-contained full template and a component-based composite template. Template-management changes can affect every application that renders by template name or UUID. Make changes in a controlled environment and keep a source copy of production templates.

Key points

• FULL templates render directly from their stored content.
• COMPOSITE templates combine a base package with ordered components.
• Composite templates must be compiled after relevant changes.
• Full templates are simpler while composite templates improve reuse and governance.
• Do not assign components to a template that is intended to remain fully self-contained.

Recommended procedure

1. Open or retrieve the intended tenant-owned template.
2. Review its mode, output, resources, and compilation status.
3. Make the smallest necessary change and save it.
4. Validate, compile when required, and perform a sample render before use.

Troubleshooting

A saved template no longer renders

Check whether the edit made a composite template STALE and compile it again.

An imported template has a different name

The importer creates a unique tenant name when a collision exists.

A resource does not appear

Confirm the resource name, encoding, template UUID, and whether the downstream renderer supports that resource type.

Related documentation

• Template Compilation Statuses
• Delete a Template
• Manage Template Resources

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.