Here’s another test for ashley
February 1, 2012 — lance_grigsbywondering if this will work …
A lot of folks these days are starting to notice WordPress’s potential to be something way more interesting than a space for a single blog. WordPress has always provided a means to aggregate content via its built-in RSS widget, which will feed data in from remote sites into a sidebar. In addition, there are–and/or were–many really handy plugins that would enable this functionality in blog pages as well, and some of the more interesting work in this area is being done in academia where instructors are using WordPress sites to 1). establish a main presence for a course where 2). all the student’s work related to said course–everything from blogs posts or content from other social media services–is aggregated into sidebars AND pages, either in the form of links or individual blog posts that get republished. For a while now, two of the more popular plugins for this have been FeedWordPress for syndicating content into pages and BDP RSS Aggregator for feeding in content to sidebars (at least, I think). Unfortunately, the latter plugin has gone the way of the dodo, but some stalwarts of aggregation are still using it even though it’s not compatible with the latest build of WordPress.
I’d like to intentionally ping two people who have introduced me to the concept of the “courseblog,” Jim Groom and Gardner Campbell, both of whom have been doing this for quite a while at their own respective universities, and both of whom have advocated the use of the aforementioned plugins (guys, chime in as necessary). In doing my own research to more fully understand the mechanics behind this approach to aggregation, however, I’m realizing that WordPress is falling short in a very fundamental way. I’m wondering: If native support for RSS is built into sidebars, why not also for pages and posts? (A recent Google search on the subject tells part of the story, but more on that later). At first glance, the native behavior of the RSS widget performs comparably to what BDP RSS could do–but maybe I’m wrong. Maybe it does more than just simple sidebar aggregation …
This conversation needs a little context, first. I’m coming at this from the perspective of a multisite admin. Since my early days of WordPressing in a multisite environment when “MU” was its own product, I learned very early on to observe certain cardinal rules to make my life easier:
Of course, I wish it were that simple all the time. However, things occasionally arise to challenge this “one-size-fits-all” approach, and this concept of aggregation is one of those. As widespread as RSS technology is, and as popular as WordPress has become for its ability to be an aggregator, there is no native support for aggregating content into the body of a WordPress site or republishing remote content into WP pages or posts. Why not? Sure, there’s old ways to hack that behavior into a theme, but those approaches don’t necessarily work in a multisite scenario where, let’s say, I have many people who want their own unique theme AND a courseblog to go with it (sure, I could hack all my themes, but getting back to #4 above … ). I’m also finding that the most popular plugins for this are either going away or are broken in WP 3.x, so what’s a super admin to do?
This is really frustrating because I’ve seen what a really fleshed-out courseblog looks like. This kind of aggregation is really valuable, and it’s one thing that–at least, not without the use of a limited amount of robust plugins up to the task–WordPress can do well. But I’d like to challenge the WordPress folks to consider making that behavior native so folks can aggregate content 1). ANYWHERE on a WordPress site, not a just in a sidebar and 2). within the context of multisite environment without the admin having to do any hacking.
Looking at WordPress.com to learn how they handle this kind of aggregation, I learned that they don’t. This thread may help explain why. While it’s true that aggregating content requires a blog admin to be more vigilant against incoming spam, it shouldn’t be a reason to keep that technology from being implemented into core WordPress.
As I’m reading Nelson’s Computer Lib / Dream Machines last night, it occurs to me that the one thing that all of our authors seem to have in common, from Bush to Engelbart to Nelson, is a sense of playfulness and an enthusiasm for what technology could be. Reading about Bush’s Memex, I sense his childlike spirit of invention without expectations or boundaries–and the really powerful part of it is that it reminds me that what humans often divine in fantasy becomes reality later on. I’m now asking myself this: Is the difference between a visionary like Bush or Engelbart and your average Joe (a.k.a., me) simply a matter of the former being able to continue that childlike tendency to wonder and invent without parameters on into adulthood, and to actually believe in those inventions?
Creativity, and the compelling attraction of the creative process, reminds me about what I liked best about school growing up: for me, it was drawing and writing stories, or really, having any opportunity to turn a blank slate into my own invention. Children are so good at this and take to it so naturally, and it’s beautiful to watch it happening (particularly when children get really excited about the creative process and get lost in it).
So, as I’m reading last night and wondering what my child’s dream machine might be, I stop my 7-year-old son as he walks into the room and give him an assignment (and one I know that he’ll love): “If you could make any kind of computer, what would it be like?” And then I asked him to draw a picture of it … Ten minutes later, he emerges from his Workshop of Wonders with the following blueprint for The Wiz Super Computer:
(It ain’t no Meta Tree Compiler-Complier, to be sure, but if this thing ever gets built in my lifetime it will really be useful helping folks get their kids out of the door in the morning.) I see his drawing and like any proud parent, I’m ready to add this work to the pantheon of refrigerator drawings, but I decide to push him a bit further … The Wiz is missing something: Documentation, perhaps? So I ask him to write some instructions for using it, and he quickly pens the following manual:
Very ergonomic indeed, but Step #2 has me really interested. A touch screen that only responds to hair and delivers an explosion if touched otherwise? I Wonder if Steve Jobs has thought of this … OK, The Wiz is really coming along, but I had one last request for my son: I ask him to explain what his machine would be good at doing, what it would be useful for. Here’s the hard sell:
So, what we have here is 1). a device that controls major household appliances with 2). a touch-screen of death that only responds to hair for the purposes of 3) impressing your friends. Note that The Wiz is particularly cool because it also looks like a robot.
What a fun diversion this was, but now back to finishing Nelson’s essay. Honestly, being a computer person, I’m feeling vulnerable at this point
.
Escarpment – Wikipedia, the free encyclopedia | Diigo. Just testing this from Diigo. Very cool.