Hi Friends, I think Maren mentioned to Carl about terminology (in a different message) and I agree that one of the most important things we need to do, is use the same terminology throughout the manual. However, that said, I'm not sure what the best way to accomplish that would be.
Actually I was going to propose some changes to some of the section and chapter titles, in this message. But now that I think about it, that might be putting the cart before the horse (as we say here, sometimes).
Should we create a Glossary? I mean as part of the manual? Or should we create a glossary that we just use for our own reference, as we write? Maybe make it part of the wiki? The gitlab wiki?
Once or twice I've had a thought about making a glossary for the website someday. But until the website contains more instructional info, it probably has no purpose yet. But what I mean is that creating a glossary, whether formally part of the manual, or just in the wiki, could also be used on the website someday.
If not glossary, what are some other ways we could keep ourselves all on the same page regarding terminology? What about one person (or 2?) who primarily takes care of that? Other ideas?
All best, brynn