CMS Plugins from an existing one

I have a wordpress plugin developed using free style. I need to redevelop & refectory it under the following Architecture discussed later. Review current old version at [login to view URL] User: admin Password: admin New requirements ===============  The frontend & backend design ([login to view URL]) . it is not responsive. It is required to design the responsive version of it to be used as plugin theme.  mobile verification new module (attached) [login to view URL]  Add chat system, by the end of a chat session you can select to add this session to TS as a new ticket. The chat box will include department & products [based on a setting option]; thus, user can choose which to connect to. Chat system should show online/offline based on if there any user login to the TS admin and its status is "available".  super admin (assign ticket to admins - set privilege to admins (who can do what[readreply-delete-close-forward(re-assign)])  Allowing trial version via robust protection to be hacked which will be checked for each site with my server, extra installation is not possible.  The New Architecture needed: 1- Based on MVC architecture. 2- Uses Multiple design pattern: Factory pattern and Table data gateway patterns. 3- Uses PHP autoloading and namespaces in all classes. (PURE OOP) 4- Follows all PSR-2 Standarads. 5- Uses TWIG as the template engine for the UI. 6- Uses CSS/Bootstrap. 7- All SQL statements are added in a new a separate layer called DAL. So in a brief, the plugin divided into 5 modules: A- Wordpress connectors : responsible for connecting and integrating the system into wordpress.(Databases, routing, static files) B- Views -> all the ui, html code. C- DAL -> Data access layers, all SQL queries. D- Controllers -> responsible for getting and passing data from/to DAL, validation, handling form actions, rendering specific View. E- Services -> responsible for ajax calls. An Example scenario when requesting the `messages` admin page: --requested URL has post-fix page=slug&scope=message&handler=index 1- WP get corresponding Controller according the slug used 2- WP-Connectors asks the ControllerFactory for the MessageController to invoke it's indexAction method. 3- The MessageController then asks the GatewayFactory for the MessageGateway to fetch few messages data from MySQL. 4- The MessageController call the twig renderer and passing [login to view URL] as the template. There's no overlapping between the above module, thus the code is pretty much neater then before. Following this design in the whole plugin, makes it really easy to maintain, refactor, design, and add functionalities to the plugin. Also, Everything is separated into components. So if you wanna run this as a standalone application, you'll only remove wp-connectors, add routing, configure DAL for the database. That's the same also, If you want later to add the plugin to another CMS like Drupal, Joomla,etc. You'll just add it's connectors and won't need any additional work A dummy code of this architecture can be accessed at [login to view URL] user: admin password: admin Your work should be ================= framework-based - php units & alpha tests - tested against Plugin-Check plugin & CMS rules & recommendations Your code should be genuine and well commented you must follow PSR standards Which CMS to be developed? ====================== We will develop the main modules, then Will develop connectors for Wordpress. Joomla, Drupal and Prestashhp With no connectors, the standalone version (php version) should work Requirements are attached again as pdf