Typo3 uses “pages” to aggregate “content” (often in columns) that is in turn shown as generated webpage to a frontend user. Pages in typo3 have own attribute sets. Beside a mandatory title also some additional attributes control e.g. visibility. Normally such attributes are modified in the backend. But maybe it’s necessary for a dedicated typo3 web application to edit page attributes too. Whatever is necessary in regard the page administration can be provided in a hidden frontend to logged in frontend users.
For example in a project MotoGo developed it was requested that the admin of a booking platform can dis- or enable the “find a room page” himself to prevent further bookings during individual timeframes. Sure the admin could login to the backend and edit the page attributes. But why shall an admin only for such a purpose be faced with a complex backend? Having a direct frontend opportunity based on a button simplified his daily live fundamentally.
Our typo3 plugin is based on our MotoGo Lib and in consequence inherits its full potential. In our base version following features are implemented and directly usable:
In case listed features aren't enough, it’s simple to add/ remove editable page fields, or verifications. Also, it’s simple to extend the base functionality with own actions alias functionalities. The simplicity of the MotoGo Lib ensures that it’s a matter of few configuration changes or additional lines of code.
Moreover, for all frontend output pure CSS, jquery mobile as well as bootstrap layout can be used. Whereby it poses no problem to use two layouts in one solution if necessary.