The module building section of the modularity docs is currently just a high level table of contents with no form of narrative to tie the pieces together: https://docs.pagure.org/modularity/development/building-modules.html

I'm thinking we should restructure that section as follows:

• Why define a module? (Explain that it allows you to branch in dist-git based on compatibility expectations, rather than being tied to the Fedora release cadence, with a default stream then being set in the System Profile for each new Fedora release)
• Naming modules & streams (the link to the formal name formatting policy would be linked from here as a subpage)
• Defining modules in modulemd (as now, but with a new subsection covering fedmod)
• Adding modules to Fedora (as now)
• Building modules in Fedora (specifically covering building with fedpkg)
• Testing modules in Fedora (expanded to also cover interactive testing with the Boltron Bikeshed image and the ./LOCAL.sh script)

/cc @langdon @asamalik @james @nphilipp