As a followup to Chas’s post regarding conductor news, I am here to report the enhancements that have been deployed.
One thing that may have gone unnoticed is the caching of some pages of Conductor. The purpose of the caching is to reduce the load time for webpages, and thus improve a visitor’s experience. We are looking at rolling out caching of other aspects of Conductor to further improve this experience. We have also brought caching to the Admin Dashboard, thus reducing the load time when you first login to Conductor.
In addition we have tweaked how Conductor interacts with search engines. First, we have added a robots.txt file to make sure that single news stories are not indexed multiple times. In a future release of Conductor, you will be able to customize your robots.txt file.
Another search related tweak is that we are making sure that search engines don’t attempt to index too far into the future in regards to upcoming events. Since Conductor dynamically generates event listing pages for a given date, search engines were more than happy to follow the “Next Year” link to infinity and beyond. But no more. Conductor stops at 2039.
We have completed several other “under the hood changes”, with a focus of providing a richer and more powerful administrative experience.
— Jeremy
