I'm considering writing literate programming docs for each file in the default Biff template. That means all of the files listed at the beginning of the https://biffweb.com/docs/reference/architecture/. Here's an example of how the docs would be formatted: http://gdeer81.github.io/marginalia/. I expect these comments would not be included when you actually generate the code, they would only be for external documentation. Also, this is just for the generated Biff template files, not the Biff API itself. Pros: • Provides an alternative path for people who want to learn by jumping directly into code. • It would be a quick reference when learning and memorizing what each file is for. • I want to standardize all my projects to follow the Biff architecture and this would serve as an informal standard for what that means, even if I'm not starting from scratch. Cons: • More docs to maintain (I'm happy to help out here) • Need to add functionality to the Biff repo to generate these docs Thoughts?