Idea for MADDUG meetup on April 4?!?

I have some Drupal 7 architecture "cases" or "problems" to present at the next MADDUG meeting.

Can we meet again at 5:30 PM CST, Wednesday, April 4? How about Essen Haus in Madison for a venue? We could have some din-din, discuss these Drupal architecture cases/problems, and have a grand ol' time. If you don't like the date/time, feel free to suggest another. I'm flexible! First round of Hacker-Pschorr (or your favorite beer or soft drink) is on me!

Here's a preview of the Drupal 7 cases I would like to discuss...

CASE #1: What are some preferred configurations of content types, blocks/panels, custom hooks, and whatever else is necessary in order to allow content editors to create their own "blocks." When I say blocks, I'm referring to any block-like approach, which can also be done with nodes, involve panels instead of blocks, etc. In this use case, the content editors not only need to be able to create their own "blocks," but they also need to be able to see only their blocks in the admin. This could possibly be mostly accomplished with Workbench Access, as we're already using that. Another very important requirement is that editors must be able to select their "blocks" on a page-by-page basis, so each page/node might display a different collection of "blocks" in the right side region. Editors also need the ability to configure the sort order of the "blocks." Ideally this would all be done with a field group in a content type that allows unlimited items. ...like select a block, and another, and another, and for each block assign a weight for sorting. The whole idea behind this case is that we don't want editors to have to monkey around in the blocks admin, mess around with URL paths, etc. We want click, click, click...

CASE #2: Given an HTML5/CSS prototype that I will demonstrate, what is the best way to use Omega or AdaptiveTheme to morph the design into a mobile version when the browser is on a mobile device like iPhone, Android, etc?

CASE #3: Content editors want a WYSIWYG editor that allows them to upload their own media, like PDFs, images, and they only want to wade through their media. They don't want to have to dig through a long list of directories, nor do they want other departments to have access to their directories. This is for a large organization with 100+ content sections. What are the best approaches for this these days using a combination of WYSIWYG and other modules/techniques?

That's it! Are you up for the challenge? ...or would you like to hang out and listen so you can apply the recommendations to your own project? Let's have a MADDUG and talk about it!

Thoughts?

Thanks,
John (TheSasquatch)