I'm sorry, I don't agree at all that your style is providing more clarity Using the committee nicknames without linking them textually to projects they relate to or ever explaining what they do makes the newsletter read like it's full of jargon only an insider can grasp, not something shorter and less dry. It does not read like you are talking to me rather than your volunteers.
What's more the Wiki Committee is careful about acknowledging the contributions of its editors, but those individuals are not on the committee itself, so equating the few people on the Wiki Committee with all of Fanlore is a bit of a disservice to them.
I can't tell who "them" refers to in this sentence. But I can't take seriously the idea that you don't want to title a section Fanlore Committee that is about the committee that runs Fanlore because people might accidentally think what? That the editors wrote this part, not the committee? So therefore you'll call the section about Fanlore something else and often never mention Fanlore within that section. This is doubletalk!
My reference to confusion over this and the internal wiki was specifically about insiders not even knowing Fanlore exists.
You can try adding hyperlinks to your website, but most people don't click that sort of link, I wouldn't expect it to help much.
I get that you want to organize your newsletter to match your internal committee structure--then it's a compile submissions from committees and paste it together job. But, your members use your products and services not the committees.
They've heard of AO3, they've sort of heard of Fanlore, but they can't quite recall the name. They may have seen TWC or it's blog, but they might not even realize they're all OTW projects--see your own survey for corroboration on this!
Your communicating in the way that reflects how you see the OTW, not how your members and users do. And to help out, you're going to link to your website, not the projects themselves where appropriate? Don't be shy folks, it's okay to promote your own projects in your newsletter.
no subject
What's more the Wiki Committee is careful about acknowledging the contributions of its editors, but those individuals are not on the committee itself, so equating the few people on the Wiki Committee with all of Fanlore is a bit of a disservice to them.
I can't tell who "them" refers to in this sentence. But I can't take seriously the idea that you don't want to title a section Fanlore Committee that is about the committee that runs Fanlore because people might accidentally think what? That the editors wrote this part, not the committee? So therefore you'll call the section about Fanlore something else and often never mention Fanlore within that section. This is doubletalk!
My reference to confusion over this and the internal wiki was specifically about insiders not even knowing Fanlore exists.
You can try adding hyperlinks to your website, but most people don't click that sort of link, I wouldn't expect it to help much.
I get that you want to organize your newsletter to match your internal committee structure--then it's a compile submissions from committees and paste it together job. But, your members use your products and services not the committees.
They've heard of AO3, they've sort of heard of Fanlore, but they can't quite recall the name. They may have seen TWC or it's blog, but they might not even realize they're all OTW projects--see your own survey for corroboration on this!
Your communicating in the way that reflects how you see the OTW, not how your members and users do. And to help out, you're going to link to your website, not the projects themselves where appropriate? Don't be shy folks, it's okay to promote your own projects in your newsletter.