Choosing the Right Tool for Tables, CSV Imports, and Structured Data in Evolution CMS

A common turning point in Evolution CMS projects comes when simple pages are no longer enough. The moment you need to create tables, import CSV data, and output structured rows on the frontend, the real question is architectural: should this still be content, or is it now application data?

There is no single answer, but the best results usually come from deciding early which layer owns the data.

A practical decision path

• Use resources and TVs when the dataset behaves like editable content.
• Use dedicated tables when the dataset is large, structured, and updated programmatically.
• Use import tools such as CSV-oriented modules when editors need repeatable bulk updates.
• Build dedicated output snippets or modules instead of trying to force raw table data straight into templates.

This keeps the system understandable. Editors work with content as content, while imported business data gets a structure designed for querying and updates.

The main mistake is trying to solve all three problems at once with one generic trick. Table design, import strategy, and output strategy should be chosen together, but they are still separate responsibilities.

Source: Evolution CMS on GitHub.