Configuring CatalogFill Imports for Structured Resource Creation in Evolution CMS

CatalogFill becomes genuinely useful when the import mapping is explicit. The original configuration showed how to describe three separate layers at once: which row type is being imported, which columns belong to core content fields, and which columns should be written into TVs.

The important part is not just the syntax of content_row and imp_content_default, but the workflow behind them. Once you define those mappings clearly, spreadsheet imports stop being a fragile one-off task and become a repeatable content pipeline.

This is especially valuable for catalogs, news migrations, and structured imports where editors need the imported resources to land already published, already on the correct template, and already carrying the right TV data.