The most important aspect of Konstrukt is to provide a set of rules, by which an application can be built. Thus it must be said to be a framework. It is however of a different kind than what most people associate with a web application framework these days.

Konstrukt is not a "full-service" framework in the style of Ruby on Rails, Zend Framework etc. Konstrukt only provides a small subset of what these do.

For example, Konstrukt provides a strategy for URL translation and URL-generation. The strategy is programmable, rather than being configurable/declarative. It takes some more effort by the programmer, but provides much greater flexibility.

* Controllers are resources
* URI-to-controller-mapping gives your application a logical structure
* Routing based on logic rather than rules
* Nested controllers supports composite view rendering
* Formcontroller provides filtering and validation

Design Goals

* Embrace HTTP rather than hide it
* Enable the programmer, rather than automating
* Favour aggregation over code-generation or config-files
* Encourage encapsulation, and deter use of global scope
* Limit focus to the controller layer