The document describes the architecture and components of the Fork CMS platform. It discusses the separation between applications, backend, frontend, API, and modules. The backend provides content management capabilities and is module-driven. The frontend serves website visitors through page-based controllers. Key aspects covered include routing, templates, internationalization, search, metadata, and an API.
28. applications - backend - frontend - api - modules
Specific base classes
‣ index / add / edit
‣ BackendBaseActionAdd
‣ create and display form
‣ BackendBaseActionIndex
‣ create and display datagrid
‣ All you have to do is add data
29. applications - backend - frontend - api - modules
Backend navigation
‣ Per module (by installer)
‣ Flexible
‣ Not limited to module context
‣ settings
32. applications - backend - frontend - api - modules
Action
‣ Controller
‣ Interface for the user
‣ Index / add / edit / delete / ...
‣ Extends from base class(es)
‣ Navigation links to action
34. applications - backend - frontend - api - modules
Engine
‣ Model
‣ Class with static methods
‣ Handles database interaction
‣ Helper
‣ Can be anything
35. applications - backend - frontend - api - modules
Ajax
‣ Controller
‣ Own base class
‣ Authentication
‣ Json output
36. applications - backend - frontend - api - modules
Cronjob
‣ Controller
‣ Own base class
‣ No authentication
‣ Collisions
‣ Command line or HTTP
37. applications - backend - frontend - api - modules
Installer
‣ Set rights
‣ Set navigation structure
‣ Set extra’s (create pages, ...)
‣ install.sql
‣ locale.xml