Help us to decide

For development, the developer would have control of the web directory structure, so it would make more sense to use the following Structure (which I currently use for the app I am developing, both in dev and production):

AppName
  -- CodeIgniter
      ---- application
      ---- system
      ---- user_guide
  -- src (the user's application source)
  -- www (all static plus the web root)
      index.php
      ---- static
         ------ images
         ------ js
         ------ css
 

You could easily add a modules folder under CodeIgniter, plus another under either www or static, with appropriate subdirectories for each module.

This is easiest for deployment (and for composer deployment especially!), and allows the end user/developer to just point the webserver at the www for webroot.

Dennis

 
Not bad idea actually. a new feature has been introduced to the 3.0 branch, this feature let developer to compress and download a module on which he's working on development environment such as wampserver, this would ease module share (for sure this feature can be disabled through the dashboard).

NexoPOS 2.6.2 available on CodeCanyon.