Wordpress is a powerful and ubiquitous tool, but it uses resources and introduces vulnerabilities. Most campuses have several instances of Wordpress running, and they are usually hacked into simple CMS functionality. We'll show you why we end up doing that and how we can set up Cascade Server to adress those needs. For the few situations where Wordpress really is the better tool, we'll give an overview of best practices for using Cascade Server's Wordpress connector while minimizing risk and upkeep costs.

1. Best Practices for Replacing Wordpress
with Cascade Server (wherever possible)
Mike Roy, Syracuse University
Wednesday, September 12, 12

2. Intro
Logic and common sense tell us to limit the use of
tools with overlapping functionality, but how?
Wednesday, September 12, 12

3. Overview
• Why?
• How?
• What?
Wednesday, September 12, 12

4. Why do people use Wordpress?
Wednesday, September 12, 12

5. (Percieved) Ease of use
Wednesday, September 12, 12

6. People like structure
Wednesday, September 12, 12

7. Don’t be shy about evangelizing
Wednesday, September 12, 12

8. Wordpress has known (and less known)
risks
Wednesday, September 12, 12

9. What is the cost
of the risk?
Wednesday, September 12, 12

10. Can we set up Cascade Server to meet
those needs?
Wednesday, September 12, 12

11. Site Clone!
Wednesday, September 12, 12

12. Themes
Wednesday, September 12, 12

13. What about when WP is the right tool?
Wednesday, September 12, 12

14. Use the plug-in!
Wednesday, September 12, 12

15. Don’t use plug-ins!
(or limit to a few you trust)
Wednesday, September 12, 12

16. Back up your database
Wednesday, September 12, 12

17. Put it in Git
Wednesday, September 12, 12

18. Thank You
Mike Roy
mproy@syr.edu
Wednesday, September 12, 12