Philip Copeland's announcement that Tim Sharp would begin contributing to the ChoralNet Blog was another small reminder of the changes coming to ChoralNet in the next few months as we make the transition from an independent non-profit corporation to being a part of the American Choral Directors Association. Tim and I have spoken often of the need for better communication with our constituents.
Towards that end I have written here before about the development of ChoralNet Communities as a major thrust towards developing a communications system for the 21st century choral world. While the surface of the ChoralNet website is not changing much right now, much is happening beneath the surface as our Manager, Martin Knowles, and Webmaestro Allen Simon are building, installing, and testing new features and tools for the communities concept.
You are already experiencing the ChoralNet Communities as you read this. This "About ChoralNet" section was created to try out some of the tools and features that will be part of ChoralNet Communities. It is very rudimentary and will have to be rebuilt when the system changes are finished; but we thought it might be instructive to see what was needed for a lay-person (me) to create and edit these pages. While I fancy myself somewhat knowledgeable about web design and formatting, in truth, web programming left me in the dust years ago. ChoralNet Communities are designed to allow anyone (even me!) to create and maintain groups of people of similar interests so that they might share information among themselves and so better the choral collective. ACDA Repertory & Standards groups, geographic groups such as state or division chapters, or any other legitimate group you can imagine will be able to organize, create forums, share files, and do other types of networking. We'll roll out the Communities at the ACDA leadership conference in late June. And it won't necessarily be limited to ACDA functions. Why not a Latin-American community? Or a choral composers community?
It was just a year ago that ChoralNet 2.0 made its debut. We hope that this new iteration of ChoraNet will be embraced as warmly as those changes have been.