The text above is live content from Cole's blog. My original blog post pointing to this static page said this:

Recently Cole posted about an interesting use of javascript to aggregate a blog feed onto another, possibly static, web page. To me, this seems far too important to let slip by. It's re-using, re-purposing content. It's providing easy author access to a page that may not otherwise offer it. Cole's post, titled Three Things, is in his own space. Please read it. Leave a comment. 

To better point out what I think is important here, after you leave a comment, check it out on my static web page (no longer necessary this is that static page). I'm pulling the most recent comment to his post and putting it on my static web page. If you comment on his post, it will update my static page. (at least I think; I'm treading on the hem of my ignorance here... ) My static page could be inside of ANGEL. The most recent comment that I'm aggregating could just as easily be anything you can post to a blog. Anything.

There's a great deal of potential here. The original feed2js script was created by Alan Levine and once sat on Maricopa Community College servers. I first learned of it there and have used it several times. The problem I saw was that the script depended on Maricopa College servers. Now, we host a version of the script. Or rather our esteemed server admins wrestled the code into submission on their servers.

I'm not a geek, but I could figure it out. And I could envision ways it could be used. Just imagine what someone with more experience could come up with!

ets version of Levine's FEED2JS service
and as hosted by the Landmark Project