-
Notifications
You must be signed in to change notification settings - Fork 1
Basic concepts # kitCommands
The kitCommands connect your application or extension with the parent CMS and bring the output exactly to the place the users of your software want it.
How does it work?
The kitFramework hook itself into the output filter of the Content Management System and listen for kitCommands. If it detect a kitCommand, it will pass the command and all parameters to the control of your extension or application and return the generated output.
The kitCommand is directly written by the user of your extension into a WYSIWYG section:
~~ sample say[Hello world!] ~~
will execute the route:
'/command/sample'
and POST all parameters, in this case the parameter say with the value 'Hello world!'.
The kitFramework will provide you also with additional information, for example if the visitor is authenticated.
Your extension can return a HTML sequence like <p><em>Hello World!</em></p> or a complete encapsulated HTML page which will be returned by the kitFramework in a specialized inline Frame.
Step into the kitCommand documentation to get more detailed information.
- If you spot a typo or want to contribute an article, a how-to or a tip, please feel free to edit the Wiki directly
- If you you have any question or suggestion, please contact the phpManufaktur Support Group
This Documentation is part of the KIT2 Project
© 2013 by phpManufaktur, kitFramework is published under MIT license.
- Silex Documentation
- Silex API
- Twig Template Engine
- Twig Short Reference
- Symfony Form Factory
- Doctrine DBAL
- Swift Mailer
- Requirements
- Installation
- .htaccess
- Configuration
- Constants
- Utilities
- Twig Extensions
- kitFramework API