Supporting a Drupal site over the Longterm


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Supporting a Drupal site over the Longterm

  1. 1. Sacramento Drupal Camp 2012Supporting Drupal Over the LongtermAnne Stefanyk (@eskimoYogi) & Meghan Sweet (@meghsweet)10 June, 2012
  2. 2. Site Launches!
  3. 3. Now What?
  4. 4. Empower Your Users
  5. 5. Drupal Web Team• Learning Drupal Takes Time• Early & Often Team Engagement• Train the Trainer• Backup Expert Level Support• Effective Documentation
  6. 6. Content Manager Training• Onsite Training Sessions• Web Team Trainers• FAQ / Forums• Help Videos• Training Materials
  7. 7. DocumentationDetailed logs in source codeExtensive commentingOnscreen helpTraining VideosFAQ Capture
  8. 8. RecruitingSuccession PlansInternshipsDrupal GiveStop Gap Solutions
  9. 9. Support Best Practices
  10. 10. Ideal Solid Foundation• UX Strategy• Documentation• Early Client Engagement• QA by Web Stakeholders• Scalable Architecture
  11. 11. CommunicationTicketing ToolExpectation ManagementExpect Ongoing Education
  12. 12. QA Best Practices• Development, Testing & Production• Stakeholder Sign-off by Review• Regular Release Cycle• Batch work
  13. 13. Audits and MonitoringPrevention is better than cure
  14. 14. Auditing what to look for:- Version Control- Hacks- Hacked! module- Custom Modules- what do they do?- Contributed Modules- updates, errors?- Custom Theme- Core- update and/or upgrade?- Live Feeds?- Site Logs- Permissions- php filter, security risks.- Spam Prevention- Performance Optimization Periodic Auditing- SEO Checklist Module is important!
  15. 15. Security Review• Input formats• File system permissions• Error reporting• Private files• Allowed upload extensions• Database errors• Failed logins• Drupal admin permissions• Username as password• Password included in user emails• PHP access Training is key. Users need Drupal awareness!
  16. 16. Monitoring- Most of the time in recovery isfiguring out what’s broken.- Monitor Trends- Use Syslog to write Drupal logsto text file- Monitor Servers, SEO- Cron- Are your admins educated?- Every time you have an issue-start to monitor.
  17. 17. Detecting Problems- Spam- number of nodes, emailsbeing sent, comments, users. (Good toknow trends) - Mollom, Captcha,Admin Views- Use Version Control to check diffs-revert to good version- Hacked! Module - switch tounhacked contrib module- Security Review Module will look forspam in content.
  18. 18. Security & Module UpdatesWhat to do with those error messages?
  19. 19. UpdatesKeep on top of Updates- within30 days at least.Finding a bug in a contribmodule.Do Not Hack Core! Noexceptions.Planning for Custom ModulesStaying in tune with Advancesin Community Modules
  20. 20. Version UpgradesTimingCommunity Catch-upNew ModulesConsider a Rebuild?TestingWhat’s the plan?
  21. 21. Community Connection
  22. 22. Groups.Drupal.orgInternal Knowledge SharingLocal User Group Meet-upsDrupal Camps, Cons & Summits
  23. 23. Taking OverAnother’s Work
  24. 24. discoveryread the documentationtalk to all stakeholdersget clear line of sight to prioritiesreview the laundry list
  25. 25. Key PointsContinual Love & AttentionKeep Documentation FreshUse good communication andfeedback/QA toolsFoster Drupal TalentCommunity Contribution
  26. 26. Thank You!@chapter_three