Docs Navigation Open
Modernizing Legacy Projects
Modernize old projects carefully by preserving what still works and replacing what no longer fits.
Legacy Evolution projects often contain years of valuable business logic and content structure. Modernization should begin with inventory, not with deletion.
Safe Modernization Flow
- list templates, TVs, snippets, plugins, modules, and extras currently in use
- identify the parts that are stable and the parts that are creating risk
- replace unsupported legacy extras with current maintained packages where possible
- clean the content model and navigation structure before adding new features
- introduce modern runtime tools only where they improve clarity or maintainability
A good modernization preserves business behavior first and improves architecture second.
Previous
Build a Commerce Site
Commerce projects mix content, catalog structure, offers, currency, messaging, and external business flows.
Next
Build a Content Site
A content site is the best first recipe for learning templates, TVs, navigation, and the resource tree.