Introduction
Basic Concepts
Understanding Routing
Controllers
Views
Assets
Modules Calling Modules
Parent & Child Modules
Database Operations
Modules within Modules
Templates & Themes
Helpers Explained
Form Handling
Working with Files
The Module Import Wizard
Authorization & Authentication
The API Explorer
If you’ve found an error, spotted something missing, or feel a section could be clearer or better explained, we’d love to hear from you. Your feedback helps keep the documentation accurate and useful for everyone.
Please report issues or suggest improvements on GitHub. Community input is invaluable in making the docs stronger.
Not comfortable with GitHub? No problem — you can also get in touch with us directly via our contact form. We welcome all feedback.
What Are Parent And Child Modules?
The Trongate framework gives developers the ability to have modules contained within modules. When a module contains one or more modules, the parent module is referred to as being a parent module. In Trongate, child modules (i.e., modules that are contained within parent modules) are called child modules.
There's no command line required and definitely no need for any Packagist, Composer or vendor/autoload!
Imagine being able to drop just one directory into your app and immediately having:
- A complete invoicing system
- A complete online shop
- A complete discussion forum
- Or, any other advanced feature that you care to imagine!
Trongate makes this possible.
All you have to do - to take advantage of parent modules and child modules - is add a module inside an existing module and also be aware of a few rules that will assist you in calling your child modules.