Book Image

Plone 3 for Education

Book Image

Plone 3 for Education

Overview of this book

Plone enables your faculty and staff to manage their own web sites, but some assembly is still required. How do you represent courses online? What about assignment schedules, lecture podcasts, and collaborative spaces? That's where this book comes in-it takes the burden of routine updates off your web team by harnessing the world's most advanced free content management system. This is the school web team's missing manual. Through step-by-step examples covering 11 common educational use cases, you'll learn how to take the box of parts provided by Plone, combine them with best-of-breed third-party plug-ins, and turn out a dynamic web environment that will be a joy to use for faculty, enhance staff productivity, and engage the student body. Plone is powerful but complex. Its ease of use for end users belies a wealth of under-the-hood features and third-party add-ons that are time-consuming for back-end web teams to sort through. The book guides you on proven paths through the forest of potential that you encounter during design and deployment, starting you with reasonable choices for each of 11 common education-domain use cases. Each one enumerates the value it brings to your site and guides you step-by-step through an implementation suitable for the vast majority of cases, meaning you can spend your time addressing the unique needs of your institutionñnot reinventing the wheel.
Table of Contents (15 chapters)
Plone 3 for Education
Credits
About the Author
About the Reviewers
Preface

Introducing the stack


This chapter is a tour through the setup of a single robust Plone server. Very large sites might need to spread across a cluster of machines, but the single-server configuration herein will suffice for 95% of deployments. As a guideline to whether you're in that 95%, here are some approximate performance metrics we're aiming for:

  • 800 anonymous requests per second (of cached content)

  • 40 authenticated requests per second

As always, premature optimization causes premature thinning of the hair, so, unless the web statistics from your old site show a strong need for more, start with a single server. It's easy to expand later.

The earlier numbers are within easy reach of relatively modest commodity hardware: for example, two 2.4-GHz, dual-core Xeons and 8 GB RAM. Plone will happily eat all the processor you can provide, performance scaling fairly linearly with CPU speed. RAM is the second most important consideration—and cheap—so don't skimp on that either.

The basic service stack...