The Mountaineers: Scaling the Heights With

PloneDavid Glick and Sally Kleinfeldt

2014 Plone Conference

Platform

Team

Chris McCullough, Matt Scholtz

David Glick, Cris Ewing, Carlos de la Guardia, Sally Kleinfeldt

Darrell Houle

Neal Maher

Jeff Bowman

Process

Step 1User Stories

Step 2ACustom Content Type Definition

Step 2BWireframe Development

Step 3Implement Custom Functionality

Step 4Theming

Step 5Bug Fixing

Quick wins

Faceted search - eea.facetednavigation

Event calendar - ftw.calendar

Feedback forms: PloneFormGen

Custom development

plone.app.widgets

Landingpages

Blog

Member accounts

Memberships

Waivers

Activity scheduling

Registration

Course registration

Rosters

Rosters and sharing

Cart and checkout

Async processing

Import and launch

Importing data

Deployment

Ongoing development

Issue management

Monitoring: New Relic

Optimization: Zope profiler

New feature development

Final thoughts

• We had our doubts at the beginning, but in the end Plone was a good fit for this site

• Jeff really took off with learning and taking advantage of the built-in content management features

• However it also gave us a reasonable platform for developing custom functionality that is tightly integrated with the content, without needing to reinvent things like local roles

• We did produce some open source code such as collective.workspace, but there are other aspects of the site, such as the cart and aspects of membership and registration handling, which could be done in a reusable way but weren’t

• This was partly due to tight schedule and budget, partly because of very specific custom requirements, and partly because we use an agile process and didn’t understand some requirements until later in development

• If some of this looks useful to someone else, we should talk about whether something can be extracted and open sourced

• It’s often easier to build something in a reusable way the second or third time once the problem space is better understood

Questions?