Understand how FeraRender assembles reusable OpenXML document templates.

Overview

Understand how FeraRender assembles reusable OpenXML document templates. Composite templates improve reuse but add a publish-time compilation step. Treat component and assignment changes as release events.

Key points

• A base package provides the OpenXML shell and styles.
• The body supplies the central document content.
• Preambles are inserted before the original body.
• Postambles are inserted after the original body.
• Compilation produces one valid word/document.xml stylesheet and one terminal section-properties element.

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

• Template Components and Component Types
• Component Content Formats
• 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.