As started on the DemoBundle in EZP-22601, KnpMenuBundle should be implemented in the kernel (or in a bundle the kernel depends on) in a way that makes it easy to create a menu based on the content structure by modifying configuration files.

More details are required, but it should involve creating one, or several, generic menu builders (see EZP-22601) that use settings to generate a menu based on the content structure: how many levels, what containers...

Note: the approach is subject to debate, since it might not be what users that are familiar with KnpMenu are expecting. It might still address the need for non Sf2 users, while making advanced users able to use the native builder or re-use parts of our integration in order to avoid reinventing the wheel.

Implementation notes

Caching

KnpMenu(Bundle) by itself doesn't handle caching, and generating a menu can be quite heavy, especially with hundreds of nodes.
This must be taken into account, by means of both documentation and proper implementation of caching with Content based expiry (the same menu will most likely be re-used on many pages, with maybe a different element selected. This could ideally be manageable, for advanced use-cases, with a client side activation of active the element).

https://github.com/symfony-cmf/MenuBundle/issues/19#issuecomment-9408782