docs: dev/web: update model/view/controller paths

Fixes #1491

docs/dev/web/controller.rst

 Controllers
 ===========
 
-Controllers live in ``/lib/gluon/web/controller``. They define which pages ("routes")
-exist under the ``/cgi-bin/gluon`` path, and what code is run when these pages are requested.
+Controllers live in the ``controller`` subdirectory of a gluon-web application
+(``/lib/gluon/config-mode/controller`` for the config mode,
+``/lib/gluon/status-page/controller`` for the status page). They define which pages ("routes")
+exist under the application base URL, and what code is run when these pages are requested.
 
 Controller scripts usually start with a *package* declaration, followed by calls
 to the *entry* function, which each define one route:

docs/dev/web/model.rst

 Models
 ======
 
-Models are defined in ``/lib/gluon/web/model``. Each model defines one or more
-forms to display on a page, and how the submitted form data is handled.
+Models are defined in the ``model`` subdirectory of a gluon-web application
+(``/lib/gluon/config-mode/model`` for the config mode; the status
+page does not use any models). Model support is not part of the gluon-web core
+anymore, but is provided by the *gluon-web-model* package.
+
+Each model defines one or more forms to display on a page, and how the submitted
+form data is handled.
 
 Let's start with an example:
 

docs/dev/web/view.rst

 Views
 =====
 
-The template parser reads views from ``/lib/gluon/web/view``. Writing own view
-should be avoided in favour of using :doc:`model` with their predefined views.
+The template parser reads views from the ``view`` subdirectory of a
+gluon-web application (``/lib/gluon/config-mode/view`` for the config mode,
+``lib/gluon/status-page/view`` for the status page).
+Writing own views should usually be avoided in favour of using :doc:`model`
+with their predefined views.
 
 Views are partial HTML pages, with additional template tags that allow
 to embed Lua code and translation strings. The following tags are defined: