The three workshops in the Program menu are all speciality workshops related to programming. It could make sense to put these in the Help menu, and I personally would probably prefer them there, as I think @gary would. But Gary and I aren’t typical users – most users will never ever ever need these wizards. If they were in the Help menu, I think they could just add to the possible confusion of new users. The Help menu is one of the first place new users will look, and it’s already a bit cluttered. I think adding items like Timer Workshop and Dialog Workshop to this menu would be even more confusing for new users. In fact now that you mention it, probably Font Awesome Icons should be moved elsewhere, probably should only be available in graphics mode (though sometimes I use it when coding also…).
I wouldn’t mind making a preference as to whether these items appeared in the Program or Help menu. Unfortunately, that’s not possible, as the Help menu is a special menu that can’t be changed on the fly, only when Panorama is compiled.
The Wizards menu was something that I originally thought was very cool and later decided was dumb. The only commonality between different wizards is that they are all implemented as Panorama databases instead of native code. Why should a user care how a feature is implemented? That’s the dumb part. So I gradually started moving each wizard to a permanent spot based on the task the wizard performed. This began with Panorama 6, but in Panorama X a logical spot for every wizard was found, leaving the Wizard menu empty.
One cool thing about the original Wizard implementation was that you could drop your own databases into the Wizard folder and they would automatically appear in the Wizard menu the next time Panorama was launched. And that still works! The Wizard folder is now inside PanoramaX.app, but it is still there and you can drop databases into it, and then a Wizard menu will appear with your database.