Control the sequence of reusable sections in a compiled document.

Overview

Control the sequence of reusable sections in a compiled document. Composite templates improve reuse but add a publish-time compilation step. Treat component and assignment changes as release events.

Key points

• Order values are evaluated within each placement.
• Duplicate order values for the same placement are rejected.
• Preambles appear before the original body.
• Postambles appear after the original body.
• Choose spaced values such as 10, 20, and 30 to make future insertion easier.

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

• Validate and Compile a Composite Template
• Manage Stale Composite Templates
• Assign Components to a Template

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.