Comparison with panels

Last updated May 18, 2010. Created by swentel on February 19, 2010.
Log in to edit this page.

People ask us how Display Suite compares to Panels. One important fact is clear: we never created this module to be a competitor or replacement for panels, in fact, most of the maintainers don't have much experience with panels at all. Somehow, features are overlapping though. Below is a list of thoughts which started on http://drupal.org/node/715316, add a comment if you want to clarify some more things. Note: we don't want to start a flamewar here, so please be gentle :)

1. With panels you can create node regions in any configuration through the UI, display suite starts you off with 5 regions, good enough for me. With panels you need to create those 5 regions on your own if you want to be able to alter sizes... That's too much clicking. DS wins out with convention over configuration.
2. The CSS altering features in DS is much easier to deal with through the UI than with Panels. Panels can also assign CSS, but it just takes too many clicks to get to where Panels gives you a huge level of layout control and localised or globalised CSS styling.
3. The drag and drop features of the DS admin UI is much much preferable to the add one by one method panels uses to assign blocks. Adding 10 blocks for each page in panels is extremely annoying, and extremely easy in DS.
4. DS has build modes, which can produce different versions of the display for different situations, ie, full node, teaser, search. Can panels do the same? There is no confirmation, if someone knows, let us know.
5. A huge difference is that DS/ND does not affect data-entry. For many sites, how good (aka professional) data-entry forms look is just as important as how the data is displayed. eCommerce websites are a particular case in point. Moreover, often it is more intuitive for users if the node display is the same as the node data-capture form - i.e. just a read-only version of it. Because DS/ND only focuses on display, web designers have two forms to think about and work on.
6. Panels offer a level of re-useability in the form of mini-panels - which can be embedded in any number of panels - this is useful also for branding.
7. Panels is heavier in terms of your effort required to achieve the required result. That is to say, there is a steeper and steepish learning curve, and more options means more decisions - aka mouse-clicks.
8. DS/ND is quicker to implement a much smaller set of data display-only layouts.
9. There is one big caveat: you may be lucky and find DS/ND does what you want, and quickly. On the other hand you may realise that you cannot achieve what you want to achieve, scrap all your work with it, and switch to Panels...
10. Panels is a superset of DS/ND.

Some thoughts we - the maintainers - can't confirm and want to handle with care. It's likely that we're going to investigate this ourselves somewhere in the future so we can add some technical documentation to this statements.

1. Panels is heavier in terms of CSS (aka browser load)
2. Panels is heavier in terms of server load (page rendering)
3. The HTML rendering is different (simple vs complex)

There is a great article by jyve written at http://www.jyvesgarden.com/blog/display-suite-vs-panels