Your SlideShare is downloading. ×
  • Like
Panopoly - Boulder DBUG 13 Nov 2013
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Panopoly - Boulder DBUG 13 Nov 2013


Presentation to the Boulder DBUG meeting on Nov. 13, 2013. Using Panopoly as the base Drupal 7 install saves time and vastly improves the content editing experience on the site. We also discussed how …

Presentation to the Boulder DBUG meeting on Nov. 13, 2013. Using Panopoly as the base Drupal 7 install saves time and vastly improves the content editing experience on the site. We also discussed how to add Panopoly to an existing site.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Obviously, I picked Drupal!
  • Obviously, I picked Drupal!
  • ResponsivenessContentFull pageLinkMediaDraft/etcDevel tabFront pageDrag & dropChange slideshowAdd text fieldChange layoutAdd view


  • 1. PANOPOLY Starting from a better place Robert Dickert rdickert
  • 2. PART I: Why Panopoly?
  • 3. Drupal’s Problem Load base WordPress and base Drupal. Which would you pick?
  • 4. Drupal’s Problem Someone shopping for their first CMS is making that comparison right now.
  • 5. What is Panopoly? • Distribution Developed by Pantheon • “Attempt to move up the stack” • Put in foundation & basics: “start building from the 3rd floor” • Contains essential modules • Preconfigured & patched • Solve a lot of your base problems • “Best of the config module space” • D8 features in D7 • Opinionated • Build your own distribution
  • 6. Why use Panopoly? D7 out of the box Panopoly out of the box • No Views • Views • No wysiwyg (and hard to • TinyMCE well-integrated set up) • No layout control • No media, slideshow; add yourself • Not responsive • Extensive panels integration • Common media add-ons (slideshow, youtube, etc.) • Responsive
  • 7. Some features • WYSIWYG built-in and integrated • Image, media, link plugins • Security (tag filters, etc.) • Layout flexibility with good UI • Landing pages can be created by non-tech users • UX features for content editors • Responsive • Search (Solr, search API) • Designed as base • Not tied to theme layer • Modular: Turn off what you don’t need • Easy to extend to build your own distro • Apps for adding prefab capabilities (blog,
  • 8. Contrib Modules used by Panopoly • admin • entity • media_vimeo • simple_gmap • admin_menu • entityreference • media_youtube • simplified_menu_admin • admin_views • facetapi • menu_block • strongarm • apps • fape • module_filter • tablefield • backports • features • navbar • token • breakpoints • fieldable_panels_panes • caption_filter • field_group • ctools • file_entity • date • image_resize_filter • date_popup_authored • • defaultconfig • • defaultcontent • • devel • • jquery_update libraries link linkit media • panelizer • panels • panels_breadcrumbs • pathauto • pm_existing_pages • respondjs • save_draft • save_draft • search_api • search_api_db • search_api_solr • uuid • views • views_autocomplete_filters • views_bulk_operations • wysiwyg • wysiwyg_filter
  • 9. How to get it • Download from and install just like regular Drupal • drush dl panopoly • Try online with Pantheon: • Project Quicksilver installs Panopoly by default:
  • 10. Demo
  • 11. PART II Adding Panopoly to an existing site.
  • 12. Issues with the existing site • Front page with panels • Fragile • Obscure method to edit • No one else can change it • Views slide show – poor admin experience • Hard to customize • Media – not a great experience • e.g., Couldn’t attach files in text (config issue?) • Content editors frustrated, page content easily broken • Dependent on one guy – me.
  • 13. Adding Panopoly: concerns • Site was not up to date (core/modules) • Already using many contrib modules used by Panopoly • Using CKEditor (Panopoly uses TinyMCE) • Would my theme break?
  • 14. The battle plan • See • Work on a duplicate on a vm • Get a module list: • drush pm-list --type=Module --status=enabled • Compare to the Panopoly contrib list • Delete matching from directory • Replace with Panopoly and enable Panopoly • drush dl panopoly • drush en panopoly_admin panopoly_core panopoly_images panopoly_magic panopoly_theme panopoly_users panopoly_widgets panopoly_pages panopoly_search panopoly_wysiwyg
  • 15. Some Details • Requires drush and some command line skills – not for the faint of heart. • Panopoly directory: /profiles/panopoly • Must set profile • drush vset -y install_profile panopoly • “Also you should” – tells Drupal to run db updates • echo "UPDATE system s SET schema_version = 0 WHERE = ’panopoly'" | drush sqlc && drush cc all
  • 16. Problems encountered And some occasionally questionable solutions… • Media & entity modules have problems • Solution: disable them before Panopoly enable • Update scripts fail trying to create tables that already exist • Solution: Manually drop the tables and rerun update (there must be a better way…) – suggestion from the meetup: tryDrush Registry Rebuild • APC module endlessly warns about not clearing • Solution: Monkey-patch code to delete the useless warning • Panelizer update script fails • Patched from • Panopoly Search just won’t install • Not really needed on this site: Left it off.
  • 17. Success! (mostly) • Took 20-30 hours for a noob. YMMV, but not trivial. • Required some config adjustments (text styles, enabled editor buttons, etc.) • Result: Close to the full Panopoly experience. • Outcomes of original concerns: • Code update: was able to get everything up-to-date no problem • Conflicting modules: caused pain (esp media), but overcame • CKEditor: magically changed over – non-issue • Theme: Also a non-issue. Theme change is next…
  • 18. Conclusions • Upgrading an existing site is possible but difficult. • For a small from-scratch site, starting with Panopoly is a no-brainer. Treat it as “core Drupal” and build from there. • Combine Panopoly with a lean VPS for the best Drupal experience. • Small-site Drupal 7 is beginning to overcome its limitations. You can have a fast, inexpensive ($5-10/mo), easy-to-use base Drupal site in minutes if you have the skills. • We need to strongly encourage people trying Drupal for the first time to avoid the base distro and use Panopoly or other good distributions.
  • 19. Questions