How can we help you?

Component Content Formats

Product: FeraRender Topic: Composable Templates Versions: Applies to all documented versions Current

Choose the correct component content format.

Audience: Template authors and developers
Recommended visibility: Public

Overview

Choose the correct component content format. Composite templates improve reuse but add a publish-time compilation step. Treat component and assignment changes as release events.

Key points

  • EDITOR_JSON stores editor-oriented source.
  • OPENXML_FRAGMENT stores literal WordprocessingML.
  • XSLT_OPENXML_FRAGMENT stores dynamic WordprocessingML XSLT.
  • Legacy OPENXML_PART and XSLT_OPENXML_PART forms are normalized.
  • DOCX and OPENXML_PACKAGE describe uploaded or packaged sources.
  • Native XSLT formats require additional permission.

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


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.