It's that time, and Panels 3 is finally getting close to beta. I have two major pieces of work to finish up (a proper preview widget and the upgrade path from Panels 5) and then I will release the first beta. I expect the first beta to be relatively unstable in terms of the features being buggy, but finally the API should be more or less stable, other than last minute fixes to get everything consistent with each other.
The beta period is a period where I feel I am going to need a lot of help. There are many outstanding TODO items (see http://groups.drupal.org/node/18765) that I simply won't be able to get to, and the bugs are likely to come fast and furious and I am hopeful to find a few good devs who can help provide solid patches and debugging to get this stuff taken care of.
Finally, there's the UI polishing. Oh the UI polishing. There are people who are going to hate the new workflows, of this I am certain. I will do my best to polish the UI and make the workflows better, but this is going to take a longer amount of time than I've really got, so we're going to launch with the weaker UI and hopefully nail up a nicer one later.
Here are some hilites of the things I really would like people to help work on:
- More content types. There are some obvious content things that could be pulled in, either in Panels itself from core, or put into other modules. Things like the forum containers, for example; having enough forum content could make it possible for Panels to take over the forum section and allow people to do more with the look of the forums.
- Styles. The 'rounded corners' style is the only interesting style we have. I'd love it if some folks would come up with some basic pane decorations. Styles have options and in theory we could implement farbtastic to do color picking and all kinds of stuff, but it'll take some effort. The idea behind color.module is solid but its very specific to themes; but we can take the ideas it used and build our styles with it. This could let a user pick a style, then pick the fonts + sizes and colors that each pane should be.
- An administrative widget. When looking at a panel page, there needs to be an easy way to get information about that page. For example, browse the contexts. Go to the the various edit points for that page. Etc. I've wanted to use admin_menu for this, but I haven't had a chance to figure out how. Maybe it needs to be its own thing. But it'd be very cool if we could have a generalized widget that Panels merely takes advantage of, rather than a Panels specific administrator.
- Better layout and style selectors. Layouts should be categorized. Like content, layout should also be able to offer subtypes. This could allow the 'flexible' type to offer many pre-canned layouts that can be tweaked, and it could also allow administrators to create layouts they want to use, save them, and re-use them easily.
Here are some hilites of what Panels 3 offers:
- A flexible layout builder. Remember that old UI where you had to say '3 columns', then hit update and get a refresh for form gadgets so you could say how wide those columns should be? No more. Now you can do a few clicks, add a column and resize it visually.
- The ability to override specific pages, and provide different output based upon what that page is displaying. This means that you can override the node page and display 'story' nodes one way, 'page' nodes another, 'article' nodes yet a third way, let 'og' nodes have their own panel displays using og panels, and finally have any nodes that are written in arabic display completely differently as well. You could also have nodes written by administrators display differently, or nodes viewed by administrators might display differently as well.
- A redesigned 'add content' modal that's much easier to use. Content in it has been recategorized so that it's more about what the content is and less about where the content comes from.
- Like Views, when editing panel objects, things aren't saved until you're completely done. This is turning out to be both good and bad.
- Layouts and styles can be offered up by themes, as well as modules.
We should be just a few short steps away from being able to have Panels take over the page and replace the blocks system entirely. We won't be there for this release of Panels 3, but maybe if some interested devs step up, we can get there.

Forum & Panels
"Things like the forum containers, for example; having enough forum content could make it possible for Panels to take over the forum section and allow people to do more with the look of the forums."
This is on the to do list for the rebuild of my Coulee Region forum so I'll just bump it to the top. :) I need to re-patch CCK and then I'll do this one. I was actually planning on putting some optional Panels integration into Advanced Forum 2.x, but that's probably a ways off.
Michelle
AX ;)
Sorry. I've been swamped with work in the past weeks.
I'll definitely have a look at the administrative interface things as soon as possible.
One thing that blocks SORELY
One thing that blocks SORELY lacks and one thing that—unless I'm mistaken—panels lacks too is revision control. We URGENTLY need revisions. Clients demand that we go back to an earlier layout or I bork something and we gotta role it back. But in both cases, it's outta sight, outta (my) mind! Can you add that into 3? Would be sooo awesome.
IMO revision control should
IMO revision control should be done through SVN or simillar. With Views, the way this works is that you modify your Views on a dev server until you like them; then you put them as default views in code, and check them into your revision control system and push them out to staging/live. If you need to roll back, the code is there.
Panels supports the same kind of export mechanisms Views does. This is a better revision control mechanism than logging every change in a database, even if it is not as fine-grained.
I understand the point about
I understand the point about SVN, but that's a lot of added complexity, which is the bane of my existence.
As a user, I see panels under "create content" which implies to me that they're nodes (if they're not then they probably shouldn't be there), which makes me wonder why there isn't revision control.
Some Using Demo Module for Rolling Back
S mather, though not designed at all as a versioning system... I've heard recently of some creative uses of the demo module that might address some of what you are looking for.
Awesome news
I've been checking the panels project page every week or so in anticipation. I'm really looking forward to this beta, Alpha4 was interesting, but still a little too hectic for everyday use;)
I am checking 5 to 10 times a day(!) :-)
Travis
>> I've been checking the panels project page every week or so in anticipation.
every week? I am literally checking about 5 to 10 times every day!(not kidding) :-)
>> I'm really looking forward to this beta
So do I. And probably many many more people.
Walter
Update on book - Drupal building blocks
Earl,
DBB is a great book and helped me get on top quite quickly. Now that panels 3 beta is released, when do you think there would be a rough cut update on panels in the book. This should be of great help to us all who have purchased the rough cut.
Thanks and once again your work is greatly appreciated.
Lynette just sent the first
Lynette just sent the first chapter of the Panels section off for editing and they usually get into the rough cut pretty quickly after that.
Panels 3
I am excited that the long awaited panels-beta has now came out. However I was wondering is it ready for production sites yet?
Is this version stable enough?
Grid Layout
I'm erasing this post for now because I found a lot of information in the panels2 API docs and am going to assume most of it still applies. Time to hit the books.
One this I am curious about is modifying/extending an existing layout (flexible). I would like to specify another 'width type' based on the 960 grid system our designers use. Any information on if this is possible/where I could start looking to implement this would be greatly appreciated.
Post new comment