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

Represent recurring events


The Recurring Events product, which comes in the p4a.ploneevent package, adds the beginnings of repeating event support to Plone, and though it's a bit buggy and in need of user interface work at the moment (such that I wouldn't recommend it for a production site), its underpinnings are well designed. An event can repeat every so many days, weeks, months, or years, and it can stop repeating on a certain date or after some set number of occurrences. Repetition is controlled through a new Recurrence tab in the event editor:

In the above, setting Repeats every to 2 would mean "repeat every 2 weeks," with 1 meaning "repeat every week". Count means "stop repeating after this many occurrences". If you provide both a Range and a Count, the most limiting one wins. And although the present interface doesn't support more complex patterns like repeating every Tuesday and Thursday, the underlying dateutil library does — so there's plenty of room for future improvement.

Spotty...