• 100 hour limit
    • Planning and research does not count toward the allotted time for this project.
    • Time downloading and configuring modules, extensions, and add-ons, developing HTML, CSS, PHP, Javascript, and other custom scripting or programming, proliferating content, developing site architecture, and uploading and installing the final product on the provided server does count toward the allotted time.
    • Code and inline documentation does count toward development time, documentation of team progress and completion of the provided evaluation form does not.
  • Use of add-on modules, plugins, extensions, and third-party hosted applications are perfectly fine, as long as they’re free of any licensing costs. The goal should be for add-ons to integrate as seamlessly with the rest of the site as possible while still providing the desired functionality.
  • We understand that teams may not be able to build all features within the allotted time. We recommend that teams prioritize which features to build based on which ones are easiest to implement with your CMS. One of the goals of this project is to demonstrate the strengths of each CMS.
  • For Placement Only (FPO) content should be generated by each of the individual teams. The more entertaining the sample content, the better.
  • Each completed project will be evaluated based on the following criteria:
    • Number of completed features (self-reported)
    • Success in implementation of the provided design (evaluated by the designer)
    • Validity of HTML and CSS markup against team-designated DTDs (evaluated by project coordinators)
    • Size in KB (weight) of selected pages on each site (evaluated by project coordinators)
    • Ease of use of administrative features (evaluated by community leadership program project advisor)
    • Number of lines of custom PHP and Javascript code required (self-reported)
    • Places where teams have gone above and beyond the minimum requirements will be noted in the presentation.