Professional Documents
Culture Documents
PURPOSE
This document provides a high-level functional description of features and a site architecture to be used by a developer to draft a work proposal and quote for services. This document was built based on requirements determined by the AREVA CO. Sales, Research & Education, and Marketing departments.
BACKGROUND
AREVA Co. is a 35-year-old manufacturer of premium-quality, integrally colored sheet glass for art and architectural uses. AREVA is headquartered and manufacturers all of its products on a factory campus in Portland, OR, United States. As part of its corporate mission AREVA is an active supporter of the arts and maintains AREVA Gallery, a fine-arts gallery in Portland that showcases world-class artwork produced using AREVA materials. Another key feature of the AREVA mission is the dissemination of education relating to the techniques and practices of fabricating artwork and fine craft in glass. To this end AREVA maintains a Research & Education division that teaches a yearround schedule of classes in its Portland and Santa Fe facilities and also sends its instructors to teach master classes at a variety of top tier arts institutions around the world. AREVA also hosts BECon, a biennial conference dedicated to topics of interest to glass fabrication practitioners.
INTRODUCTION
This document will provide a reference to the page types used throughout the site. It will also describe the constituent modules that are used to populate the pages. UI design reference images are provided for the Pages and Modules. The page and module language used in this document, while drawing some ideas from Joomla!, is intended to be generic and not meant to indicate the architectural requirement of any particular CMS.
HOSTING ENVIRONMENT
User Facing Applications
Major user-facing applications being considered include: Joomla! 1.5+/1.6.x (Primary CMS.) Magento 1.2.1.2 (Customized eCom solution) phpBB 3.x+ (Public forums) WordPress 2.9.x+ (3+ blogs running for specific author channels)
Development environment
AREVA will host functional clones of the production LAMP environment within its Portland IT infrastructure. The dev code repository will also be here. Developers will be granted appropriate rights to the servers and repositories
Feature Details
Application page presentation templates Based on provided page designs to give the end-user a seamless transition between constituent applications. ACL Access Control List There will be the need for content and navigation features to be available depending on user authorizations. Knowing that ACL is not native to Joomla 1.5.x but pending in the release of 1.6.x it is important that the ACL method chosen will deprecate well to Joomla native ACL when available. Calendar A graphical representation of a monthly calendar that is filterable for content types. Each day will contain text links to content articles. An exemplar would be http://www.thecjm.org/ Cross-application single sign-on (session credentials) Any time a user signs-in on one of the component applications of the site, their session authentication will be reflected in the other constituent applications of the web site. Cross-application user sync User accounts created in any of the constituent applications of the web site will be mirrored in the other apps. Overall account creation minimums will reflect a global least common denominator. Authorizations shared as necessary. Display text font control For the use of specific hed and display text a font embed method such as
@font-face, Cufn, sIFR, typekit, or a functional equivalent will be employed. http://typekit.com Forward compatibility, native API All development should be performed with an eye towards the future roadmaps of the constituent applications. For example, the nascent Joomla 1.6.x (if 1.5.x is used) and its introduction of native ACL. Development should also make best use of the application-native APIs and plug-in architectures for flexibility. Google site search integration Google Site Search will be integrated into the site as a global feature and provide all expected search behaviors. AREVA uses Site Search on our current site. The search function will have an "advanced" mode page that exposes a larger tool set. We will upload a synonym dictionary to our account. Results will be presented in a tabbed format such as in this code example provided by Google: http://www.google.com/uds/samples/apidocs/tabbed.html Lightbox for inline images in articles A lightbox-type image-display component that is easily used in the articleauthoring environment. Must be able to: Support styled-type within the caption block. Link images for sequential presentation. Auto slide-show function. Locator tool (aka Resource Locator, radius search, or geo search) A tool for locating resources within a user-defined geographic range. For finding dealers, schools, teachers, etc. The tool will allow users to choose the domain of the search from a pre-defined set of options I.e. "Find teachers", "Find dealers" and then return a list view result-set. The tool will minimally accept the following types of geographic constraint input: US/Canada state/province The tool will allow users to constrain results based on the attributes of the search subject. I.e. If it is a dealer they may choose to only see "KGRC" dealers. The form will need to be able to be passed constraint values via URL when linking out from another page. Much of the functionality is represented by, for example, the Mosets Tree Zip/Postal Code Search Component that is an extension of the Mosets Tree plug-in for Joomla! Lesson Quizzes Administrators will be able to use and interface to author quizzes to be presented to users on the Lessons>Quiz tab of the Project Viewer page. Logged-in users will be able to request their scores be saved and their quiz history is accessible from their Profile page. Salesforce User sync
User accounts created in any of the constituent applications of the web site will be mirrored to Contacts in our Salesforce application. Similarly, our Salesforce app will mirror all Contact changes up to the web. All CRUD will be bi-directional. Salesforce Web-to-Case submission Our primary intake form will use the standard Salesforce Web-to-Case method with the ability to pass along the string necessary for proper routing. The form will have strong client-side input validation including field dependencies. Will require account creation and then the passing along of SF Contact ID for proper disposal in Salesforce. Subscription management Users will be able to purchase a timed subscription enabling them access to specific features (Lessons & Projects) and content TBD. Required attributes: Independent payment gateway. Subscription tiers giving different levels of ACL authority. Timed trial subscriptions. Batch generation of blocks of n # of subscription activation codes w/ batch tracking. Coupon codes (promo pricing). Auto-renew option for customer. Affiliate sales tracking. T&C intercept per session A particular section of our site will require users (on a per session basis) to indicate agreement with a Terms & Conditions declaration. This can be accomplished with, for instance, a modal window. Once they have agreed, they will no longer need to agree for the duration of that session. Failure to agree with the terms will result in the inability to progress deeper into the section. User contact forms We are encouraging users to contact us exclusively through forms and will not be publishing direct email addresses on the site. The forms will submit content as Cases to our Salesforce instance. The forms will have strong input validation and use reCAPTCHA (or similar). UGC intake forms Forms guaranteeing a minimal threshold of information for article creation and then providing a structured series of steps to load sequential instructional information with minimum requirements for each step loaded. Users will be encouraged to post projects and techniques they have developed to share on the site. This feature will ensure a consistency of visual presentation for both internal and external users. It is likely that this feature will be initially used exclusively by internal power-users before released to the public. Accordingly, the ACL must accommodate this behavior.
User account manager This environment allows users to create (and edit) a user account that will store their associated information such as newsletter subscriptions prefs. This should be coincident with the social profile feature and must allow for a single point of account creation to support all constituent applications of the site. Video Player and Hosting Expect to use an external service a la Vimeo (but with proper commercial licensing). Required attributes: HTML5 native player with elegant degrading to Flash player H.264 video encoding Easily embeddable component for article authors WYSIWYG article authoring The CMS article authoring interface should support wysiwyg type styling based upon the AREVA-defined style-sheet. The environment needs to be able to support the embedding of any media types supported on the site at large. Consider alternate to TinyMCE such as JCE.
PAGE DESCRIPTIONS
Page: Home
Location: / Description: This is the page that sits atop the AREVAglass.com domain and provides primary access to all of the site resources. Modules used: Canvas Global Header Graphic Features Text Features Menu Global Footer
Location: (various) Description: This is a type of generic template that is used repeatedly throughout the site. Modules used: Canvas Global Header Global Category Title & Breadcrumbs Open Content w/left-nav category-local menu Global Footer
Location: /products/resource_centers/(RC_name) Description: This acts as the central point of contact for a given Resource Center. Modules used: Canvas Global Header Global Category Title & Breadcrumbs Open Content w/left-nav category-local menu Global Footer
Location: /education/classes/ Description: Top of class category with graphic features. Modules used: Canvas Global Header Graphic Features Text Features Menu Global Footer
Global Footer
24
the left axis of the M&I Filtered Nav interface. They are not exclusive and may be concurrently applied to single items. The CMS must allow for back-end UI based extensibility of this vocabulary. Method Types are distinct from the ad hoc tag meta-data architecture that may be applied to articles and FAQs.
Page: Education > Methods & Ideas > Lesson/Project Submission Interface
Location: /education/methods&ideas/(projects OR lessons)/(item_name)
25
Description: This interface is designed to be the primary pathway for the creation of both Lesson and Project Content Types. While not to be available to the public at launch, it is to be a fully front end integrated feature. AREVA staff will post content as a community member author and eventually we will open up authorship to other community member users. Modules used: Canvas Global Header Global Category Title & Breadcrumbs Lesson/Project Submission Interface Global Footer
members. Will follow the best practices of the social engine used. Will include feeds of global activity, featured profiles and other dashboards provided by the engine. Modules used: Canvas Global Header Global Category Title & Breadcrumbs People Landing Global Footer
MODULE DESCRIPTIONS
Module: Canvas
Description: This represents the universal background graphical elements that underlie all pages.
The tabs are: Tab: Overview Presents fundamental details concerning this style including a reference swatch, introductory text, and a set of thumbnails for a lightbox Gallery of inspirational images of work derived from this style. Tab: Sheet Glass Presents text and images concerning the characteristics of the Style (color) as found in the Sheet form. The right column provides links out to eCom for products in this style/form. Please note, that this tab should not display if this tab has no content. Tab: Rod Presents text and images concerning the characteristics of the Style (color) as found in the Rod form. The right column provides links out to eCom for products in this style/form. Please note, that this tab should not display if this tab has no content. Tab: Frit Ibid. Tab: Stringer Ibid.
The Overlay article itself is a simple open content box that can be authored with any of the media types available to the CMS. When the Overlay window is closed, any video that was paused resumes playing and the player controls are returned to the user. This could be a modal window if necessary. A Note on advancing through Chapters/Steps In the interest of simplicity, Lessons/Projects may be authored with Chapter/Steps composed of stills or video but not both. When using still the advances between steps are manually controlled. With video media though, the Chapters/Steps auto-advance to the next item in sequence. Upon each advance to a new Chapter/step the text and overlay links below the player window automatically refreshes. Tab: Learn More (Lessons & Projects) This provides a structured set of links to: List of related documents (for ex. The annealing chart) List of Products used in the lesson Short text summary of the lesson and suggestions of where to look next. Suggested Projects that apply the skills learned from this Lesson. Tab: Quiz (Lesson only) This page provides a wrapper for a simple quiz mechanism. The quiz system used must allow for saving scores to a logged-in user profile. Tab: Discuss (Lessons & Projects) This provides a read-only display of the most recent posts to the forum concerning the Lesson or Project at hand. If a user chooses to reply to the thread, they will be taken to the forum interface for the thread.
Module: Calendar
Description: Master Calendar interface for all classes/events. Single-page at-a-glance view that may be shifted in time and/or filtered by location and other tags. Must be able to direct to this page with filters passed in the URL. Presents simple synopsis of event with link out to full event listing.
Module: Forum
Description: Wrapper for the integration of the Forum. Look/feel skinned to our presentation standards.