If you're one of those people who wants to help with Views, but you have no idea what to do, and your helping is going to require me to spend more time explaining the architecture to you than I would spend actually getting work done, your help is not valuable to me.

Sorry if this comes off as mean, but right now I'm a giant freakin' obstacle and I'm getting a little tired of having it pointed out to me twice daily, with a whole bunch of people offering to help, but few apparently willing to do things the Drupal Way and just read the damn code, figure out what needs to be done and do it.

Kent Bye did a fantastic visualization of putting together a cheap taxonomy/term page override. It helps to have already created this when looking at it, but it does give an idea, at least, of what's going on.

Click here for full-sized version

Download here: http://drupal.org/node/194291

Finally!

The context system I described in my last post exists.

People are working on some demos and walk-throughs to show people how to utilize this new system. It takes a little bit of stepping through to understand the potential, and I suspect there will be some disappointment at the content that is available; but that's a piece where I can very much encourage people to help.

In Panels, Context is lingo for a wrapper around any significant object. By default, Panels supports 'Node', 'Taxonomy term' (and terms as mentioned above), 'Taxonomy vocabulary', and 'User' as contexts.

These contexts can get into a display in more than one way; right now, there are three ways that a panel page can acquire a context: