Your SlideShare is downloading. ×
BADCamp 2012- Drupal Support
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

BADCamp 2012- Drupal Support


Published on

Supporting a Drupal Site over the Longterm.

Supporting a Drupal Site over the Longterm.

Published in: Technology
  • 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


  • 1. BADCamp 2012Supporting a Drupal Over the LongtermAnne Stefanyk (@eskimoYogi) & Meghan Sweet (@meghsweet)4 November, 2012
  • 2. Site Launches!
  • 3. Now What?
  • 4. Empower Your Users
  • 5. Drupal Web Team• Learning Drupal Takes Time• Early & Often Team Engagement• Train the Trainer• Backup Expert Level Support• Effective Documentation
  • 6. Content Manager Training• Onsite Training Sessions• Web Team Trainers• FAQ / Forums• Help Videos• Training Materials
  • 7. DocumentationDetailed logs in source codeExtensive commentingOnscreen helpTraining VideosFAQ Capture
  • 8. RecruitingSuccession PlansInternshipsDrupal GiveStop Gap Solutions
  • 9. Support Best Practices
  • 10. Ideal Solid Foundation• UX Strategy• Documentation• Early Client Engagement• QA by Web Stakeholders• Scalable Architecture
  • 11. CommunicationTicketing ToolExpectation ManagementExpect Ongoing Education
  • 12. QA Best Practices• Development, Testing & Production• Stakeholder Sign-off by Review• Regular Release Cycle• Batch work
  • 13. Audits and MonitoringPrevention is better than cure
  • 14. AuditingPeriodic Auditing is important!Make a check-list.
  • 15. Auditing Code Base- Hacked! module- Custom Modules- what do they do?- Contributed Modules- updates, errors?- Drupal Core- update and/or upgrade?- Comments in code- Drupal Coding standards- Red flags
  • 16. Auditing Development Environment- Version Control- Development Server Setup: Dev > Test > Prod-What is the development workflow?
  • 17. Auditing Configuration- Panels/Context/Display Suite, used properly?- Live Updating? Feeds?- Site Logs- Permissions and Roles- PHP filter- Spam Prevention- Performance Optimization-SEO Checklist Module
  • 18. Auditing Theme- Are themes up to date?- Base Theme used? Or Hacked?- Custom PHP logic in tpl files?- Javascript Libraries- CSS structure- Responsive- What techniques?- Red flags- are tpl files out of control?
  • 19. Auditing Performance- Front End-PerformanceCaching, CSS/JS aggregation, Images- Backend PerformanceSlow custom code, out-of-date modules, caching- Server performance- Traffic Levels- anonymous or logged in.
  • 20. Monitoring- Most of the time in recovery is figuring out what’s broken- Train your clients how to monitor and write good tickets
  • 21. Monitoring- Use Syslog to write Drupal logs to text file- Cron and caching configured and on?- Total Admin Control or create admin views- Are your admins educated?- Every time you have an issue- start to monitor.-Google Analytics
  • 22. Security Review- Most security holes are created in the configuration andtheme.- Security Review module will help!
  • 23. Security Review- File system permissions- Input format- Content (nodes, comments and fields in Drupal 7)- Error reporting- Private file- Allowed upload extension- Database error- Failed logins- Drupal admin permissions- Username as password- Password included in user emails- PHP access
  • 24. Training is key.Users need Drupal awareness!
  • 25. Detecting Problems- Spam-Mollom, Captcha, Admin Views- Use Version Control to check diffs- revertto good version- Hacked! Module - switch to unhackedcontrib module- Security Review Module will look for spamin content.- Use a good hosting company
  • 26. Security & Module UpdatesWhat to do with those error messages?
  • 27. UpdatesKeep on top of Updates- within 30 daysfor security updates.Read the update notes for non-securityupdates.Finding a bug in a contrib module.Do Not Hack Core! No exceptions.Planning for Custom ModulesStaying in tune with Advances in
  • 28. Version UpgradesTimingCommunity Catch-upNew ModulesConsider a Rebuild?TestingWhat’s the plan?
  • 29. Community Connection
  • 30. Groups.Drupal.orgInternal Knowledge SharingLocal User Group Meet-upsDrupal Camps, Cons & Summits
  • 31. Taking OverAnother’s Work
  • 32. discoveryread the documentationtalk to all stakeholdersget clear line of sight to prioritiesreview the laundry list
  • 33. Key PointsContinual Love & AttentionKeep Documentation FreshUse good communication andfeedback/QA toolsFoster Drupal TalentCommunity Contribution
  • 34. Thank You!@chapter_three