Learn Drupal's Most Powerful Site-Building Modules: Display Suite, Context, Views, & Panels

Editor's Notes

• #2: \n
• #3: 1. Today I will attempt to give a good overview of how Context, Panels, Display Suite and Views work together on a site.\n2. I’ll talk pros and cons and about my strategy with using these tools\n3. I have lots of screenshots and examples to illustrate how to use these tools to construct a site\n
• #4: \n
• #5: \n
• #6: \n
• #7: \n
• #8: 1. Over 1 million downloads and yet a lot of people I talk to at these camps don’t use these tools regularly or don’t know a lot about them\n
• #9: 1. Over 1 million downloads and yet a lot of people I talk to at these camps don’t use these tools regularly or don’t know a lot about them\n
• #10: 1. Over 1 million downloads and yet a lot of people I talk to at these camps don’t use these tools regularly or don’t know a lot about them\n
• #11: 1. Over 1 million downloads and yet a lot of people I talk to at these camps don’t use these tools regularly or don’t know a lot about them\n
• #12: 1. One way to deconstruct a site design is to see blocks and fields\n2. A block can be just about anything, a blurb of information, a dynamic list, a menu, a field\n3. A field is pulling a specific piece of information from a piece of content \n\n
• #13: 1. One way to deconstruct a site design is to see blocks and fields\n2. A block can be just about anything, a blurb of information, a dynamic list, a menu, a field\n3. A field is pulling a specific piece of information from a piece of content \n\n
• #14: 1. One way to deconstruct a site design is to see blocks and fields\n2. A block can be just about anything, a blurb of information, a dynamic list, a menu, a field\n3. A field is pulling a specific piece of information from a piece of content \n\n
• #15: 1. One way to deconstruct a site design is to see blocks and fields\n2. A block can be just about anything, a blurb of information, a dynamic list, a menu, a field\n3. A field is pulling a specific piece of information from a piece of content \n\n
• #16: 1. Even if you have a simple page you might still think of it this way\n
• #17: 1. Even if you have a simple page you might still think of it this way\n
• #18: 1. We just talked about dividing a page design into blocks and fields. I also separate Content from Pages.\n
• #19: 1. We just talked about dividing a page design into blocks and fields. I also separate Content from Pages.\n
• #20: 1. We just talked about dividing a page design into blocks and fields. I also separate Content from Pages.\n
• #21: 1. We just talked about dividing a page design into blocks and fields. I also separate Content from Pages.\n
• #22: 1. We just talked about dividing a page design into blocks and fields. I also separate Content from Pages.\n
• #23: 1. Let’s talk tools!\n2. We’ll talk Pages first, what are our options for laying out blocks on a page?\n3. This is a Drupal 6 example of the Admin Block Page and an example of where it can get messy.\n
• #24: 1. Context in my view is a lot better for laying out blocks\n2. More of a learning curve perhaps, but can be more organized\n
• #25: 1. This is a OpenChurch ‘global’ context example illustrating how blocks are arranged into theme regions\n2. There are more options than just blocks\n
• #26: 1. The Admin module has a nice UI tool for modifying contexts inline\n2. And Contexts are exportable!\n
• #27: 1. I have given some presentations on Features several times and so a big emphasis for me is exportability\n
• #28: 1. Now Let’s talk Panels\n2. An aside, “Panels Everywhere” controls the whole page’s layout and is interesting although outside of the scope of this discussion.\n
• #29: 1. Now Let’s talk Panels\n2. An aside, “Panels Everywhere” controls the whole page’s layout and is interesting although outside of the scope of this discussion.\n
• #30: 1. Now Let’s talk Panels\n2. An aside, “Panels Everywhere” controls the whole page’s layout and is interesting although outside of the scope of this discussion.\n
• #31: 1. Now Let’s talk Panels\n2. An aside, “Panels Everywhere” controls the whole page’s layout and is interesting although outside of the scope of this discussion.\n
• #32: 1. Panels does have a nicer inline editing option called IPE which is illustrated here on the homepage\n
• #33: 1. Panels does have a nicer inline editing option called IPE which is illustrated here on the homepage\n
• #34: 1. Now let’s talk tools to build content\n2. Can arrange fields just using the Drupal UI and you have some flexibility\n3. This is exportable to Features\n
• #35: 1. You can also use your theme to customize content\n2. Can have more control\n3. You have configuration store in code, version control, etc.\n4. This is pretty straight forward until you have to do ‘dynamic’ things, then things can get hairy\n
• #36: 1. Now let’s look at how Panels can be used for building content pages\n2. When I figured out Panels node template I stopped using the theme layer at all for nodes or user customizations\n3. Not going to cover Panelizer\n
• #37: 1. Now let’s look at how Panels can be used for building content pages\n2. When I figured out Panels node template I stopped using the theme layer at all for nodes or user customizations\n3. Not going to cover Panelizer\n
• #38: 1. Now let’s look at how Panels can be used for building content pages\n2. When I figured out Panels node template I stopped using the theme layer at all for nodes or user customizations\n3. Not going to cover Panelizer\n
• #39: 1. Now let’s look at how Panels can be used for building content pages\n2. When I figured out Panels node template I stopped using the theme layer at all for nodes or user customizations\n3. Not going to cover Panelizer\n
• #40: 1. This illustrates the friendlier inline editor we saw earlier\n
• #41: 1. This illustrates the friendlier inline editor we saw earlier\n
• #42: 1. This is another way to edit that same page we were looking at\n2. This screen is more controversial, some people like it, some hate it\n3. Panelizer is probably a more friendly way to handle this\n
• #43: \n
• #44: \n
• #45: \n
• #46: \n
• #47: \n
• #48: \n
• #49: \n
• #50: \n
• #51: \n
• #52: 1. This is pretty cool...\n
• #53: 1. Drupal comes with a couple, ‘Default’ and ‘Teaser’, many modules add additional view modes as well\n2. This screen just determines where the new view mode will show up\n
• #54: 1. DS gives you new layout options on the Drupal Manage Display Page\n2. It’s interesting that Panels & DS layouts are interchangeable\n
• #55: 1. This is a custom layout I defined in the theme layer which is pretty easy (works with Panels too)\n
• #56: 1. This is a custom layout I defined in the theme layer which is pretty easy (works with Panels too)\n
• #57: 1. We’ve talked tools for building pages and content, now let’s talk about pulling content\n
• #58: 1. We’ve talked tools for building pages and content, now let’s talk about pulling content\n
• #59: 1. We’ve talked tools for building pages and content, now let’s talk about pulling content\n
• #60: 1. Most developers know Views, but I want to talk a little strategy\n2. In Drupal 4-5 I used to use node and I would find out pretty quick that the customer wanted to display content differently depending on the ‘context’ of where the content was being displayed. Having 1 ‘Teaser’ display mode was not enough. This led to node.tpl.php craziness!\n
• #61: 1. Most developers know Views, but I want to talk a little strategy\n2. In Drupal 4-5 I used to use node and I would find out pretty quick that the customer wanted to display content differently depending on the ‘context’ of where the content was being displayed. Having 1 ‘Teaser’ display mode was not enough. This led to node.tpl.php craziness!\n
• #62: 1. Most developers know Views, but I want to talk a little strategy\n2. In Drupal 4-5 I used to use node and I would find out pretty quick that the customer wanted to display content differently depending on the ‘context’ of where the content was being displayed. Having 1 ‘Teaser’ display mode was not enough. This led to node.tpl.php craziness!\n
• #63: 1. Most developers know Views, but I want to talk a little strategy\n2. In Drupal 4-5 I used to use node and I would find out pretty quick that the customer wanted to display content differently depending on the ‘context’ of where the content was being displayed. Having 1 ‘Teaser’ display mode was not enough. This led to node.tpl.php craziness!\n
• #64: \n
• #65: \n
• #66: \n
• #67: \n
• #68: \n
• #69: \n
• #70: \n
• #71: \n
• #72: \n
• #73: \n
• #74: \n
• #75: \n
• #76: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #77: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #78: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #79: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #80: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #81: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #82: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #83: 1. The main reason why I wanted to bring up views was to talk about views & DS\n
• #84: \n
• #85: \n
• #86: \n
• #87: \n
• #88: 1. I use Panels primarily for page layouts where the layout is different enough to justify\n2. The Panels UI is just too outside of the Drupal UI, mixing Panels with Context is confusing\n
• #89: 1. I use Panels primarily for page layouts where the layout is different enough to justify\n2. The Panels UI is just too outside of the Drupal UI, mixing Panels with Context is confusing\n
• #90: 1. I use Panels primarily for page layouts where the layout is different enough to justify\n2. The Panels UI is just too outside of the Drupal UI, mixing Panels with Context is confusing\n
• #91: 1. I use Panels primarily for page layouts where the layout is different enough to justify\n2. The Panels UI is just too outside of the Drupal UI, mixing Panels with Context is confusing\n
• #92: \n
• #93: 1. Could be a panel\n2. Could use context for some persistent elements\n
• #94: 1. Could be a panel\n2. Could use context for some persistent elements\n
• #95: 1. Could be a panel\n2. Could use context for some persistent elements\n
• #96: 1. Could be a panel\n2. Could use context for some persistent elements\n
• #97: 1. Let’s Look at this page again\n2. This could all be context\n3. A tie breaker for me is how different this is from the normal layout of the rest of the site\n
• #98: 1. Let’s Look at this page again\n2. This could all be context\n3. A tie breaker for me is how different this is from the normal layout of the rest of the site\n
• #99: 1. Here is a content page example\n
• #100: 1. Here is a content page example\n
• #101: 1. Here is a content page example\n
• #102: 1. Here is a content page example\n
• #103: 1. Here is a content page example\n
• #104: \n
• #105: \n