Panels 2 is a module that uses drag & drop to add content to layouts. It is designed as an API so that modules can use these displays to customize their own areas, and we're working toward fully integrating this solution into Drupal 7.
Panels 2 allows you to override the Edit form of a node. The advantage is clear for developers and non-developers as well, as placing difference blocks in different places is all made through an easy to use UI.
Let's override the Edit form of all the story nodes and divide it into two columns. On the left will place the content form, and on the right the node comments.
- In the panel settings 'Add' a 'Two Column' panel.
- Panel name = Override node edit
- path = node/%/edit
- Click 'next'
Last updated by joachim on Fri, 2008-11-21 10:40
Attaching some thoughts on how to improve the organisation and layout of the panels administration pages. I started pasting this together before I coud see that the img tag is allowed in wiki pages. Let me know if you'd like a certain screenshot to be instantly visible here. I have an .ODT of this document as well but that's bigger than the 1MB limit for attachments here.Read more
Help brainstorm and or volunteer to help out with Panels 2 documentation.
Below is in an initial outline that is based on looking at Views documentation as an example, talking to merlinofchaos, and pondering what might be helpful. Constructive comments, additions, offers to help do specific sections are welcome and encouraged.
I. Panels 2 documentation
+Top level: brief overview of Panels 2
- Panels basic options
- Panels displays
- Panel pages
- Panel nodes
- Mini panels
- Panels Plugins (See the demo module at Panels Plugin Example module
- Argument Plugins
- Context Plugins
- Relationship Plugins
- Content_type Plugins
II. Panels 2 Theming
III. Panels 2 tutorials
In case I want my detail page ($page=1) at /node/123 of my own content type to display in a panel - how would I do this?Read more
Is there an easy way to start an embedded view in panels2 at a certain offset, other than writing my own module and setting $view->offset from the panel arguments in my implementation of hook_views_pre_query?
For a news site, I want the first article to look different and the layout prevents me from just formatting the first list item differently. Instead, I want to have two panes where the first one shows only the first item, the other pane shows items starting from the second one.
I just proposed this session for Barcelona. Hope it makes sense.
Looking deeply at the MySite / Panels integration question, I think what we need is a unified abstraction API that lets modules find, collect, render, and display data in multiple contexts.
Working on a unified API might be the best direction. Take a look at the session proposal and this brief overview.
For a current project, I am using panel pages, integrated with menus created from a taxonomy hierarchy. For this, I have done a mashup module of taxonomy_menu, taxonomy_assoc - which in my case associates a panel page with a taxononomy term - and panel pages. The code for the resulting module is attached to the slides of my presentation at FrOSCon in Sankt Augustin today.Read more
in my site i have used block cache with panels for caching tabs panel.
First i have created mini panels with tabs (last items,more view,more voted) for any contents (news,events...) .
After i have added this mini panels in panel page in home using the block cache version for caching it.
My ideas is of add cache capacibility for any type of contents in panels (view,block,nodes and custom contents) with the same options in block cache:
-cache per user
-cache per page
-cache time limit
-cache where a node is creatred,updated,deleted
-cache when login/logut
what you think?Read more
I started looking at MySite/Panels integration today. From my end, the obvious starting point is making MySite-defined content available as Panels.
- MySite currently defines 14 plugin types (+3 contribs), which would explode the options available to Panels.
- MySite now has a mysite_display() function that makes accessing a MySite content element possible from within another module or theme.
Here's the issue I ran into, and it may be that I simply haven't dived deep enough.Read more
Updated: Dec 11, 2007
Additionally, the following items are currently in progress:
panels_mini.module -- this module will create panels that will be exposed as blocks. I.e, the panel within a panel. A good use is to put a bunch of content in a one column panel, and then put that throughout the site.
- panels_profile.module -- A panel that will let every user have their own display to edit their profile page. This is an outward facing page, and lets users have significant amounts of control over their "my account" page. This is sort of the starting place for a myspace type site.
panels_node_decorator.module (what a lousy name) -- lets you control node pages with panels. Should offer fine control so that nodes with different types or different taxonomy will get different displays.-- this is no longer necessary as panels pages came up with a clever way to do this for free.
- panels template -- will allow your theme to use panel layouts instead of page.tpl.php, and use the panels layout engine to lay out your entire site.
- new CCK integration -- integrate panels with CCK. At the very least, the 'node reference' and 'user reference' relationship, all by itself, would add immense power to Panels.
- new Documentation. There are two forms: User documentation; there is an outline for that on a wiki page in this group. Please help. The second form is API documentation.
For some of these, there isn't a lot of design yet, just some ideas. This is the place to come to discuss the features these should have, and additional modules that can utilize Panels.Read more