The FvwmModules are bits of software launched from within FVWM using the 'Module' command to add more functionality and versatility to the Desktop. There are a hand full of different modules out there, but the main ones I'm gonna focus on in this part of the guide is the FvwmTaskBar, FvwmPager and FvwmButtons. To launch a module you first need to configure it and then launch it using the Module Command. These modules will all use colorsets as an option, so I will first generate two colorsets to be used though out the module section. The three main modules, FvwmTaskBar, FvwmPager and FvwmButtons can all use RootTransparent colorsets, so if you like transparency feel free to make these colorsets RootTransparent like for the menu. To my knowledge the Translucency patch only affects menus and Translucent colorsets cannot be used.

#####
# Module Colorsets
###########
Colorset 9 fg rgb:00/00/00, hi rgb:00/00/00, sh rgb:00/00/00, bg rgb:e9/e9/d9
Colorset 10 fg rgb:00/00/00, hi rgb:dd/00/00, sh rgb:dd/00/00, bg rgb:fb/fc/ec

To see how the basic syntax for module configuration works, lets take a look at the FvwmIdent Module. This module is used to identify a window and gives us info about it that can be useful in configuring fvwm. As with most things in FVWM the first thing that should be done is to destroy any previous config. After that send some options to the module as follows:

#####
# FvwmIdent
###########
DestroyModuleConfig FvwmIdent: *
*FvwmIdent: Colorset 9
*FvwmIdent: Font "xft:Sans:Bold:size=12:antialias=True"

The config for this module is quite simple, I just tell FvwmIdent what font and colorset to use. To launch the module, just add 'Module FvwmIdent' to an action (such as I have in the window ops menu).