This walkthrough guides you through JiNexus Framework's MVC pipeline — from module configuration and route matching to controller dispatch and view rendering — so you understand how each component fits together when building your application.
Every request to a JiNexus application passes through this pipeline:
public/index.php) loads Composer
autoloading, reads config/application.config.php, and hands it to
ApplicationFactory::build().
modules.config.php, instantiates its Module
class, and merges all getConfig() arrays together.
Route component, which derives the current URI from
$_SERVER and looks for a match.
indexAction()) is called.
Below is the complete skeleton application structure:
application_root/
config/
application.config.php Module list reference
modules.config.php Enabled module namespaces
data/
cache/ Cache directory (writable)
module/
Application/
config/
module.config.php Route and view-manager config
src/
Module.php Application module class
Controller/
IndexController.php Default controller
view/
application/index/ View templates
error/ Error page templates
layout/ Layout templates
public/
index.php Front controller (document root)
.htaccess Apache rewrite rules
asset/ Static assets
test/
Application/ Unit tests
vendor/ Composer dependencies
Each directory and file is covered in detail in the walkthrough pages that follow. Start with the Module Manager section to learn how modules are registered and configured.
If you found a typo or error, please help us improve this document. Create Issue