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.