Collecting knowledge generated during these modules

[JasonJWilliamsNY]

During an on-boarding session (April 12) it was suggested that we have a concrete way to capture knowledge generated during these modules. This issue is a placeholder for that discussion to think about how that knowledge could be explicitly captured. Maybe a single issue, perhaps multiple, perhaps something else?

[zkamvar]

This was brought up in the bootstrap session today and I think one solution is to use this list to compile a sort of "Flight Rules" that lives in the "extras" section. For example, we have a list of github flight rules for maintainers: https://github.com/carpentries/maintainer-resources/blob/main/FLIGHT_RULES.md