Ever since the first release of Display Suite, people have been asking if it is a replacement for Panels, and what the differences are between the two. The answer is not an easy one since each module has its own strengths, but there is an overlap too. Without going into a detailed write-up of the two modules, I will focus on pointing out their main strengths and main differences, so that it might be easier to choose which one you need for your project.
Panels
Panels is a very powerful module with a huge amount of options. Let's look at it's main features:
- You can create a Mini panel, which is a block that you can assign a layout to (e.g. three columns with a header above), and then in each of the regions in that layout, you can combine several pieces of content such as a node, another block, custom content, a View etc.
- You can also create a Panel node, which is very similar to a Mini panel, but instead of a block, you create a node, giving the benefit of having a URL and page title. In a Panel node it is just as easy to choose a layout and assign all kinds of content to it.
- Even more powerful is Panel Pages. Without it being an actual node, you can build up your entire page with all kinds of content and elements and assign a URL to it. The drawback against a Panel node is that this Page will not show up in search results for example.
- Important in the comparison with Display Suite is the fact that the Pages system also allows to overtake default system layouts such as the node detail layout. That means you can restructure the way a node is displayed on its detail page e.g. put the comments on the right, the links just below the title etc. Based on a variety of parameters such as the language or node id, user id etc, you can even create several versions of the node detail page.
To summarize, Panels offers the option to mix together different objects together on one page.
Display Suite
For those who don't know the Display Suite, I advice to read my short introduction on it. For others, I will make a short recap of it's features in light of the comparison with Panels.
Display Suite allows you to manipulate the way objects such as nodes, users, comments etc. are being displayed in several different locations throughout your site. Two examples of its usage:
- Rearrange how the fields for a certain content type are being displayed on the node detail page, in a teaser view or in the search results.
- With the custom build modes, you could create a 'Block list' build mode and configure it to show just your node title and its taxonomy tags. The Views integration then allows a View with for example 'related content' lists in the sidebar to use this build mode instead of being limited to 'full' and 'teaser'.
The differences
- The Display Suite always starts with a single object such as a node and offers a way to configure its display by rearranging the fields for that node in a fixed 5 column layout.
Panels is focused on combining different objects such as blocks, nodes, Views etc. together in a variety of layouts. - As mentioned, Panels Pages offer the option to change the layout of the detail page of a node and you have the option to create several variants based on arguments.
With the Display Suite you can define the layout of your node detail, but it does not take any arguments. On the other hand, through its 'build mode' system, it extends far further than just the node detail page but is able to configure the layout of your content in the search results, teasers etc. - Double nesting: In DS, you can put your fields in one of the 5 regions, but inside those regions, you can also group them together in fieldgroups.
Panels is restricted to one level of grouping.
Making them work together
Ironically, the best way to explain the difference is to show how well they integrate with each other. Two examples:
- When you create a node panel for the homepage, you can decide to throw in some custom blocks and some nodes. For those nodes, Display Suite adds a 'build mode' dropdown to the panels form, offering the option to decide which display to use for that node in the Panel. So Panels allows you to combine everything on one page, and the Display Suite handles the way the nodes in that panel are displayed.
- Panel Pages allows to take over the Drupal search page, so you could move around all elements of that page. For the actual display of the search results, you can use the 'search' build mode in Display Suite to define what fields to show for which content type.
Conclusion
If you only want to take control of the display of your nodes in different build modes and get rid of template files, use Display Suite.
If you need to make complex pages where different elements have to be combined together, use Panels.
Personally I prefer to use the two of them together, where Panels is a great help in building a homepage and landing pages, and Display Suite helps to keep the management of the layout of all the different objects easy as pie.
Do you agree, or have I missed out on something? All feedback is welcome!
Comments
I too agree the combined approach of using DS and Panels together. Alternative to using DS and Panels would be to use Omega Theme + Delta + DS + Context, which is slightly less flexible than DS + Panels, but it gives a lot of advantages too (e.g. 960gs for one).
I'd say, go for DS and Panels if you use Zen / Adaptive, etc, and drop Panels if you use Omega Theme :)
Great summary. I like the combined approach. I agree that the two modules can work together perfectly. Have you tried it with the Omega-theme?
They work great togheter ! With Adaptiuve too it work well. ;o)
I haven't come to test the Omega theme yet, but I've heard good things about combining the two.
Informative, thanks :)
It would be very helpful if you please provide your thoughts about using DS and context simultaneously.
Use case is as follows:
- Would like to use DS as content layout modifier and for reaction rules to add dynamic behavior to control the elements of the content.
Really sorry, but haven't ever really worked with Context, maybe you could post your question in the Display Suite issue queue on drupal.org?
Omega Theme comes with a Delta module, which allow you to create different arrangements of the fields and create a "Delta" for it. You can use these "Deltas" as Context reactions. I think Delta supports DS as well. Really powerful :)
Many thanks.
You have saved me some time.
Magnífico artículo, muchas gracias.
A great article, thank you very much.
Wow nice article. With some test I made on my side I agree with you. Use both to obtain the best of the two world !!!
The article is good. But you float image of the social bookmarking buttons is making it very annoying and difficult to read the article. Please get rid of them or place them on the other right hand side.
Very annoying and difficult would be to read this while waiting for a tsunami to hit or for nuclear melt down up the road.
Great article, very interesting suite which I am only just discovering. Thanks.
Didn't even notice the social bookmarking buttons. ;-)
I'm a bit confused by this: "The drawback against a Panel node is that this Page will not show up in search results for example."
Should this be in the previous paragraph? or do you mean that the Panel Page will not show up on the search results?
Hmm, it does not seem really relevant now that I am reading it again. But yes, I did mean that a Panel Page will not show up in the search results, as it is not a node.
Hello,
I'm currently building a intranet site and for the presentation of a team, I need to display a view in two columns. Another thing to know, this view will be displayed within a panel.
So, I have a view with 7 fields (the fields title, a lightbox picture, a text field "team", "fonction", "office", "phone number" and "email adress"). The style of this view is set in "views accordion" for my needs and when I use both "views accordion" and "display suite fields" combined, I have to display the photo field in a left column and all others fields directly in the right column...
When I use display suite fields and put the photo field in the left region, the title field in the header and all others fields in the right region, there seems to be a big bug with the style view accordion...
I hope you Jyve will help me because I don't know how to set all that stuff correctly :)
Thanks in advance.
>Panels is restricted to one level of grouping.
No it´s not cause you can "rewrite" outputs and e.g. use fields/entities again which also allows grouping.
However I think that this is not a "vs"-thing cause you can combine both very well.
My most liked feature of DS are the additional "view modes".
Thanks for this article.
For your projects, are you only using panels and/or DS without creating regions and blcs in the page.tpl.php-file ?
I still use the page.tpl file to define my regions, and I only use node panels to divide the content region into more 'subregions'. With Panels Everywhere you might get to a situation where custom regions/blocks are no longer necessary, but I personally don't take it that far.
Thanks for a clear and helpful article
Understandable and clear for newbie too. Thanks
"In DS, you can put your fields in one of the 5 regions, but inside those regions, you can also group them together in fieldgroups. Panels is restricted to one level of grouping."
I think this is inaccurate: in Panels you can always create a mini panel first, and put that into another panel (page or node) afterwards. This way you can implement any nesting you need, even with arbitrary depth (but possibly at the price of higher complexity).
Great article.
For complex sites I would indeed use both tools alongside each other. A powerful and genious combination. Excellent write up.
Hello:
May I translate this article into traditional Chinese? I'll mark the copyright and your url. The translation will be posted at my blog and Drupal Taiwan Forum.
saa
Sure, no problem! Be sure to post a link to the article, i'm curious to see what it looks like in Chinese :)
Quite simple and Very clear. thanks pal.
Good read. Thanks.