Sean mentioned he has updated the Mach-II Development Guide. It now makes reference to mach-ii.info. Thanks, Sean. Here are the release notes:

Release 1.2:
Contents: updated to 1.0.10 core files, added mach-ii.info as a reference site;
Concepts: added note that listeners straddle the line between Controller and Model, clarified that Mach II itself recognizes request.MachIIConfigMode as a default (if present);
Structure: added suggestions for keeping listeners separate from the business model (or at least easily identifiable);
Models: fixed typos in example code ("cfJoe" and Dave Knapik); tried to clarify the queuing nature of events; elaborated on invokers and type safety; rewrote confusing DAO/memento paragraph and commented out example implementation of DAO/gateway; further clarified transfer objects and their use; added specific reference to the mach-ii.info sample application;
Views: recommended unqualified event over request.event in views; added section on paramterized views and the concept of exit events (from Fusebox), added recommendations for using append=;
Event Handlers: added verb.noun as an acceptable alternative for event names, as well as additional partitioning event names;
Event Filters: fixed typos in example code (Hugo Ahlenius, Tracy Logan);
Plugins: no change.

This job posting was submitted to the Mach-II mailing list the yesterday.

I'm looking for developers familiar with the Mach II framework, in
Irvine, CA. Rate is $55k - $65k + benefits depending on expertise and
experience. Please contact me at ton- AT pts1.com if interested. Thanks!

If you apply for the job, good luck!

Have you created a collection of CFCs for others to use? Are you looking for a way to create documentation for those components? If so, you should check out CFCDoc, a documenation generator for ColdFusion Components. Here's an example of Mach-II documentation generated by CFCDoc.