pertemplate

Pertemplate is a concept in template rendering that refers to associating configuration, data context, or rendering behavior with an individual template rather than applying settings globally across all templates. The term combines per and template and is used to describe a pattern that makes templates more self-contained and portable.

Implementation typically involves per-template metadata, template-scoped variables, or dedicated per-template configuration objects that are read during rendering. Some engines provide a top-of-template metadata block, while others use a per-template context that can be supplied when the template is compiled or rendered. This enables different templates to specify their own data sources, formatting rules, conditional logic, or localization settings.

Common use cases include localizing output for different regions, applying different currency formats, date formats, or feature flags per template, and isolating template behavior to reduce cross-template interference. For example, a receipt template may specify currency USD and a short date format, while a statement template uses EUR and a longer date format.

Benefits of the pertemplate approach include greater flexibility, modularity, and ease of reuse, as templates become more independent from a shared global configuration. Drawbacks include increased configuration complexity, potential duplication of logic, and added considerations for caching, validation, and documentation to prevent inconsistencies.

Pertemplate is supported to varying degrees by modern template systems, particularly those that emphasize component-based rendering or context-rich templates. It complements concepts such as template inheritance, scoped variables, and metadata-driven rendering.