Shopkeeper 1.0 and the Shift Toward a Separate Product Table

Shopkeeper 1.0 was important because it moved beyond the idea that every store should keep all product data directly in ordinary MODX documents. The release highlighted a more scalable approach: storing products in a separate table when catalog size and structure started to outgrow the simplest document-only model.

Why that shift mattered

• it gave bigger stores a more realistic data model
• it reduced pressure on document-based content structures for purely catalog concerns
• it marked Shopkeeper as a more serious ecommerce layer, not just a small add-on

Historical significance

This release is worth remembering because it reflects a broader pattern in Evolution: once projects became more commerce-heavy, the community kept looking for cleaner separations between editorial content and product data.

Why this belongs in the timeline

This post matters because it shows how Evolution CMS teams solved real project problems with small, explicit patterns instead of heavy abstractions. That practical, incremental style is one of the clearest through-lines in the old Evo ecosystem.