The Curricular Technology team did a lot of brainstorming over the summer. This seems like a good time to step back and compare what we have done to what our priorities are:
We have a lot of projects started whose focus is to find one or more replacements for Segue including a CT feature matrix, a CT needs “knowledge grid” (i.e. what do we know and not know about technologies that faculty and students need), course site platform survey questions.
Bryan and I were chatting after the last CT meeting. Bryan had an interesting idea for how Curricular Technology documentation could be aggregated on the LIS site. We both agreed that we need more than simply a list of links to documentation sites. Instead of just links, we should have some explanation of the resource/site being linked to, some sort of abstract describing that resource/site.
Bryan suggested that rather than writing abstracts just for the CT landing page, we could pull in actual content from those resources using the Drupal Views module. Essentially, if I follow Bryan’s explanation (see whiteboard diagram), each CT resource would defined as a particular content type which the views module could be configured to fetch from that source, be it WordPress, Segue, eRes or Drupal.