Skip to content
prod 352bb92
Browse

Tagged: zajmodules

All Tags
zajmodules
9 pages
5 related

Pages with this tag

Implement Customizations

1

Add custom features to a CodeCanyon Laravel app without losing them on the next vendor update — the ZajModules + vendor-customizations system.

1 · The decision rule

2

Three 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

3

Build 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 · Restore customizations

4

Re-apply your vendor-customizations overlay with the restore script after the clean vendor/ rebuild, re-scan for backdoor signatures, confirm every ZajModule, zajm_ table, and _zaj column survived untouched, verify the patches behaviourally, then deploy staging-first.

Zaj module deploy

5

Deploy or update a ZajModules package — autoload dump, config publish, provider check, instant disable rollback. Peeled from MWF2.

Architecture & systems

6

The bird's-eye view of how a Zajaly-style CodeCanyon Laravel app fits together — the four pillars, the event-driven flow, and where each piece is executed.

Laravel/CodeCanyon — Handbook

7

The mental models behind running a CodeCanyon Laravel app — when a change is a module vs a customization, where admin files live, how to extend the schema safely, and how to version your fork.

ZajModules vs customizations

8

The core mental model — deciding whether a change is a new ZajModule, a vendor customization, or a schema extension, and why that split keeps your app update-safe.

Customization decision

9

The 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.