Blog Sections Open
Which Extras Belonged in the First Evolution Repository?
An early ecosystem discussion about what the Evolution package repository should include first and how priorities shape a healthy extras surface.
When the first dedicated Evolution repository was taking shape, one of the most useful questions was also the simplest: which extras should appear there first? The answer mattered because early repository choices define user expectations and influence the whole package ecosystem.
This discussion is valuable because it captures the priorities of the time: editors wanted proven workflow tools, developers wanted reusable building blocks, and site owners wanted confidence that common needs were covered by discoverable packages.
Why Repository Curation Matters
- the first visible packages define trust
- good defaults reduce fragmentation
- a curated repository helps teams find supported solutions faster
Source: original community announcement.
Persisting Shopkeeper Cart Sessions in the Database
Why storing cart sessions in the database can improve reliability and let visitors return to partially filled carts later.
What Power Users Would Still Simplify in the Evolution CMS Manager
A reflection on which manager functions felt unnecessary or overly heavy, and why backend simplification was an important part of long-term Evolution CMS usability.