GHOP: #134: Create a short screencast introducing Panels 2

The GHOP task associated with this issue can be found at:
http://code.google.com/p/google-highly-open-participation-drupal/issues/...

The node created for this task can be found at: http://drupal.org/node/210208

I don't have time now to watch the screencast, but noticed a few things:

1.) I didn't see a CC logo as recommended at http://drupal.org/node/62196. You can just add that to the beginning probably. It would also be nice to have a title screen at the beginning and at some point display the link to the handbook page you created.

2.) Add a link to your handbook page from the blip.tv video page.

3.) You might try to expand your handbook page outline/script a little. But since I haven't watched the video, maybe it's as expanded as it needs to be. It just looked skimpy at first glance, but I see you've linked to your previous tutorials, so I guess there's more to it than meets the eye.

I'll try to take a look at the video sometime soon. I'll leave the status here as needs review since these are all pretty minor issues.

Aha, thanks.

I didn't go with a full script, because it seemed unnecessary when the whole screencast is based on tutorials (which I link to).

I am not sure I can add a CC to the video now, but there is a CC notice on the right column.

I added the link to the handbook page on the blip.tv.

Just watched the screen cast and let me say first that you did a very nice job. IF there is one complaint its no instructions on mini-panels which I am very interested in. +1

I'd be happy to do a minipanels screencast when it is fixed (for GHOP or not for GHOP).

Being involved with Panels 2 documentation specifically, instead of jumping around, has made me a lot more effective. I'm not going away any time soon.

Also, the frontpage tutorial was omitted from the screencast, simply because it had to be under ten minutes. Again, I'd love to do a screencast of that, for GHOP or not for GHOP.

Awesome job. I've marked the Google task complete.

As someone who hasn't been following panels very closely, this is a nice overview! Really gets me excited about trying panels out. There are some edges that could be smoother:

(Before I go further, I'm assuming the audience is a "general" developer. Knows what a module is, but may not know PHP)

As already mentioned, it would be nice if it started with some kind of title card. For a second I wasn't sure if I had missed the intro.

I'm not sure the version information at the beginning is "evergreen." This is a nice overview and may be used for some time. Also, it would be nice if you talked a little about what "panels" is supposed to accomplish.

Since this isn't a comprehensive overview, you might consider skipping the "import" comment and go right to "add".

The "CSS ID" field is probably worth just mentioning since it will most likely be necessary later. Same with CSS fields in your first example. Nothing major, but friendly to noobs.

The path field info might be a little unclear to the new user. Consider mentioning that this is the URL of the page. (Same for your variable example as well)

It's cool to skip the "Advanced Settings" fields, but it might be nice to acknowledge them, not explicitly, but saying "we're going to ignore these advanced settings for now." (Just like the arguments page)

I didn't mind that you skipped actually doing a mini-panel, but to keep this evergreen, consider not mentioning that it doesn't currently work on your machine. You're not obligated to build out everything, especially to keep things short.

For your second example it might have been nice to use a different column layout, just for variety.

I hope that's helpful. I really like what you've done so far!

oops, fixing status

Those are great suggestions, and since I've already claimed another screencast task I'll keep that in mind.

However, this task is fixed, so I'm marking it as such.

multitask meltdown!! Should be fixed

Hehe, np :)

I'm aiming to make a lot more screencasts, and this was my first so I skimmed a bit on the edges. They should improve over time, and now I know where to improve.

This is a great start! I'm all fired up to try panels out, so you accomplished the most important bit ;-)