We need a common way to end chapters, a conclusion of sorts.
- "In this chapter you learned ..." (Boilerplate concluding paragraph)
- Summary of chapter themes
- List of review questions (good for individual or group stud, etc.)
- List of key terms
What are your ideas?
What do you like?
This issue arose recently as we were editing the forthcoming chapter on
project and community governance, so I'm pleased to see the discussion
taking place here and on GitHub.
The Open Organization community tends toward the "review questions"
route, but that's largely because we also release books in print and
know that others use them for study and book club sessions. The
questions, we're told, are good fodder for sparking broader
conversations. If that is a vision and/or goal for this guidebook, then
I would suggest that approach.
Otherwise, I tend to like the "summary of themes" approach. We ask each
author to condense three to five core ideas from the chapter and write
them in one or two sentences (max), then collect those in a concluding
section called something like "Chapter Review." This is also a great
resource for reproducing elsewhere (on a home page, when someone asks
"What's this chapter about, anyway?" etc.)