firstspirit-templating

Page templates in FirstSpirit use `$CMS_VALUE` and `$CMS_IF` instructions to bind content fields and conditionally display elements. Define input components, apply rules for validation, and reference system objects like `#global` to access metadata. The skill provides syntax examples and architecture patterns for implementing forms with inheritance.

FirstSpirit separates templates by function: page templates define store-level structure; section templates organize content blocks within pages; format templates handle reusable content components. Each template type applies different rules, system objects, and metadata inheritance patterns documented in the skill's template-types reference.

`$CMS_IF` evaluates expressions to display or hide content based on variables and metadata values. Pair it with `$CMS_VALUE` for field access and `$CMS_FOR` for loops. The skill details syntax, supported functions like `if`, and how to reference system objects to build dynamic, responsive templates.

Yes. FirstSpirit metadata inherits across the six-store architecture through template configuration and system objects. Define metadata at template and store levels, apply rules to enforce consistency, and use snippets for rich content previews. The skill covers metadata setup, inheritance rules, and workflow integration.

Core syntax includes `$CMS_VALUE`, `$CMS_IF`, `$CMS_FOR` instructions for accessing fields, conditionals, and loops. System objects like `#global`, `#for`, and `#style` provide runtime context. The skill centralizes syntax definitions, data types, functions, and expressions across all template types and stores.