Tagged: customization
Pages with this tag
Implement Customizations
1Add custom features to a CodeCanyon Laravel app without losing them on the next vendor update — the ZajModules + vendor-customizations system.
1 · The decision rule
2Three questions that route any change to the right update-safe home — a ZajModule package, the vendor-customizations overlay, or a _zaj migration that adds marked columns to a vendor table — so nothing you build is lost on the next vendor update.
2 · Build a ZajModule
3Build new functionality as a self-contained ZajModule package under packages/ZajModules/ — directory structure, namespace and naming conventions, and the event-driven pattern that keeps it isolated from vendor code and safe across updates.
3 · Vendor customizations
4When a vendor file must be edited, store the edited copy in the resources/vendor-customizations/ overlay that mirrors vendor paths, mark your changes with ZAJ:BEGIN/END markers, and re-apply the overlay after every composer install overwrites vendor/.
4 · Track and restore
5Keep a MOD-NNN tracking log and a _CUSTOMIZATIONS file documenting every vendor patch, and run restore-vendor-customizations.php to re-apply your overlay automatically after composer install or a vendor update overwrites vendor/.
Laravel/CodeCanyon — Cheat sheets
6Glanceable command and decision references distilled from the five CodeCanyon Laravel playbooks — deploy commands, the customization decision, and common gotchas.
Customization decision
7The one-screen routing for any change to a CodeCanyon Laravel app — vendor file edit → vendor-customizations overlay, new functionality → ZajModule, vendor-table column → additive _zaj migration — so nothing is lost on the next vendor update.