so here is a mapping of my plan for a UBC content management strategy. It is designed to overcome two obstacles:

1) Content changes, therefore the content stored in repositories has to change and be updated when the source is updated. This is overcome by using a wiki (this has been Novak’s vision of content management for a while) that produces RSS feeds along with an aggregator like Feed WordPress that updates the repository when a feed gets updated (that feature is still buggy at the moment, but I will get to fixing that ASAP).

2) The second obstacle is the fact that RSS and JavaScript are not easily searchable (a must for a content repository or even an end user site). Republishing is a must until we find an easy way to index and search RSS and JSON.

So here is what it looks like (click on it for larger view):