You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daniel Kvist edited this page Aug 8, 2013
·
3 revisions
Here's a backlog of ideas that can be used in future sprints.
Menu system and content types
The current menu system allows for adding and removing menus and menu items through the use of plugins. This could be expanded to allow the admin UI to create, update and delete menus and menu items as well. For this to be useful however, some type of 'content type' system might be beneficial to create. It would allow an administrator, teacher or student to create different types of content which could be organised into different menus shown for different users.
Another addition to this would be to refactor out the hardcoded php pages that now exist in the system. These php pages does nothing more then instantiate a controller and call its 'go' method to generate the content. This could easily be done through storing controller name/path in the database instead.
Core refactoring to plugins and Plugin-API extension
The core contains a lot of functionality that could be rewritten into plugins. This might increase the understanding of the Plugin-API and how it can be used and would most likely give the developers new ideas on functionality that the API could offer.