Create reusable PREAMBLE, BODY, POSTAMBLE, and BASE_PACKAGE components.

Overview

Create reusable PREAMBLE, BODY, POSTAMBLE, and BASE_PACKAGE components. Composite templates improve reuse but add a publish-time compilation step. Treat component and assignment changes as release events.

Key points

• PREAMBLE and POSTAMBLE components can be assigned around a template body.
• BODY and BASE_PACKAGE identify architectural component roles.
• Components have tenant ownership, active state, dataset association, and version.
• Global components may be visible alongside tenant components.
• Changing a component invalidates compiled templates that use it.

Recommended procedure

1. Confirm the base package and body are compatible.
2. Select active preamble and postamble components.
3. Set deterministic placement order.
4. Scan, validate, compile, and render a regression sample.

Troubleshooting

Compilation reports a declaration conflict

Rename or centralize variables, parameters, or named templates that share a name but differ in content.

The component order is rejected

Use unique sort-order values within PREAMBLE and POSTAMBLE.

Rendering returns TEMPLATE_COMPILATION_REQUIRED

The compiled package is absent or stale; validate and compile before rendering.

Related documentation

• Component Content Formats
• Assign Components to a Template
• Order Preambles and Postambles

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.