Modular MVC

The core of every Trongate application is the modules directory. Each module is self-contained, independent, and built with Native PHP - no Composer, no PSR-4 autoloaders, no hidden bloat.

Modules: The Only Part of Your App That Matters

Everything else is plumbing.
Your actual app? It lives in modules/. One folder per feature. Done.

Here's an example of a real-world Trongate module:

Key Characteristics

• One controller file per module. Required.
• One model file per module. Optional.
• A views/ folder. Optional.
• CSS, JS, images? Throw them in too, if you want. Optional.
• Child modules inside modules? Yes. Nesting allowed.

The Benefits of Modular MVC

• Copy → paste → works. No setup. No config. No faffing about.
• Don't like models? Fine. Write 50 lines in the controller. We don’t judge.
• Need models? Cool. Keep your controller skinny. We respect that too.
• Assets live with the code that uses them.
  No more hunting through massive and confusing paths, such as:
  public/assets/js/admin/users/whoops/wrong-folder
  .

How Trongate Modules Destroy “Traditional” MVC