"History"

Configuring a custom bundle (cacp) is the 2nd part of a bundle tutorial series - both part originate from blog posts from Grégory Joseph. (Blog post have ben deleted, I have been figured out recently).
This page (cacp) describes explains two "tricks":

"turning" a webapp into a Magnolia module

which can have a module version handler and a module descriptor.
I always liked that one.

However, the next one seems much more important, since people ask for it now and then.

usage of module version handler

It starts with the section Customizing configuration by code and explaining usage of module version handler class.
This section is most probably the only "useful" source concerning module version handling among the complete docs. It shows with minimal examples
how you can execute tasks (typically changing JCR config) 

• during installation
• during update

Tasks

Minimum

• Write a new page Using module version handler
  • Reusing section Customizing configuration by code of the cacp page
  • Title, intro should contain terms module version handler, configure module to boost them for google search
  • rather not mentioning "turning" a webapp into a Magnolia module on this new page.

Open Question(s) 

• Should we keep the above described 1st part?  Should we create a distinct page "Turning a webapp into a Magnolia module"?
• Is the content of Customizing configuration by code of the cacp page enough for the new page Using module version handler?

..