Site Specifications

#Site Specification Document

#Welcome / Home Page

##Top Navigation Logged in users will have links to go directly to their Chapter/Teams and personal content/dashboard areas easily. Links to TeamSpeak, and Who is online information will also need to be readily accessible.

##Chapter navigation Chapters need to be easily accessible via the ZGC-Front page.

##Inter-site links Inter-site links to other partner websites need to be included, such as those found on the top-navivigation of http://blog.thezeitgeistmovement.com.

At this time of writing, these are:

• TZM Global
• TZM Blog and News
• ZeitNews (Tech)
• Zeitgeist Media Project
• Zeitgeist Media Festival
• ZDAY Global

##Introductory information Anonymous users should see on the home page some general information about what this website is, why they might want to join, and further information such as links to the main TZM website for orientation material.

##Carousel of images with supporting text All Teams/Chapters as well as the front-page portal will have a image-carousel available to them where they can post images with supporting text and links that rotate [cross fade, or slide] between the different top-news items.

##Single sign on in the ZGC website when navigating between various Chapters, and Teams. Upon logging in, users can switch from one Chapter to another, or to a Team on ZGC without needing to log back in again.

##Membership Anyone can join the ZGC website. Users may then request to join a regional Chapter or a official tzm Team. Users may need to be approved (by someone with the appropriate role) before being active in the selected Chapter/Team.

##Personnel Profile (+Skills) Registration should allow entry of a user's skill, education, experience, interests, resources and availabilty. This information will be used by tzm project managers who are seeking volunteers for teams and projects.

##Chapter Site Visibility Welcome / Informational page, chapter newsfeed, chapter calendar events, site-wide links specific to any chapter, and chapter registration are all visible to anonymous users. Chapter members have access to view and edit Chapter related content. Editing and creating of content depends on the specific Role of the user. Members who are not members of the chapter, can see all documents that the Chapter member can see, but with read-only access.

TODO: Wireframe

##User Dashboard customization Allow the user to customize the view of widgets that they see or can hide from their User Dashboard.

TODO: Define widgets ##Default User Dashboard Default User Dashboard needs to be configured to include the most common and useful widgets.

TODO: Define widgets ##Tasks System should provide a means to create Tasks and to assign them to a user in a particular Chapter/Team or a Project within a Chapter or Team. You should also be able to see all tasks assigned to a particular Chapter/Team via an overview page. While Users would see tasks assigned to them in their personal dashboard or at the Chapter or Team page level.

##Messaging Allow users to communicate with one or more users though a message functionality. Messages will be sent to their email address, as indicated in their profile.

##Tags Allow for blog posts, calendar event, pages, polls and other content to be tagged with taxonomy terms for classification. Vocabulary of taxonomy terms will be free-entry where anyone can add a new term. System will suggest terms as you type so that you can pick pre-existing ones [to somewhat reduce duplicates]. User's can pick whatever terms they feel matches the subject of the content, such as "occupywallstreet" or "zday20Essential2"

##Calendars Each Chapter/Team will have its own calendar where events can be placed, with detail pages and supporting images.

##Subscription and notification management Allow the user to subscribe to the activity of a (Chapter/Team) or a content thread. Email can be configured to include new activity details. Allow for the user to decide if they want to receive email or only see new items online, and at a choice of intervals. And allow for user to unsubscribe as needed.

##Media embedding Allow users to upload images into the comments-fields and into other content types such as documents, blogs or events. Allow links, such as video (youtube/vimeo) to embed without having to upload.

##Search/filter tools Searching options should include the ability to restrict results to ZGC-Front-Page, and/or (all/specific ) Chapter/Teams. User's should also be able to filter their results to a specific kind of content; such as Blog pages, Forum posts, Documents/Resources etc.

##Translation i18n & l10n both the templates and content

##Data integrity System's database should be frequently backed up off-location to at least 2 other countries than the country in which the server is located; preferably to nations that are also non-allied with each other. Access to the data should also be distributed to many people in many countries whom we can trust.

##User Roles The system should support various Roles that users can be assigned to, so that various privileges can be given to allow/dis-allow use of various aspects of the system. Details of what the roles are and their privileges TBD in further documentation.

##Chapter/Team Projects Within each Chapter/Team, Projects can be created. A Project is a single-page with a description that you make and then use to assign Tasks to. Projects are therefore related to goals which have ongoing or completion dates. Users can filter Tasks by Project in addition to being able to filter by Sub-Group/sub-team.

##State/Country/regional Chapters Users will be able to enlarge the scope of the information they are viewing to be Regional/State/Country wide. Users can browse up and down the regional level to get wider or more specific information. A coordinator of a particular regional/country-level Chapter can also promote and add their own News items and descriptive content to the consolidated stream of information.

##Security Team A team of people should be available that we can email, and contact for ongoing security concerns. This team should also be proactive in testing for attack holes and listening to various lists for updates that might be required to seal-off our systems. [Wireframe]

##Regional Chapter Management A regional state/country chapter will have its own Team-area to manage itself (calendar, forum, blog, tasks etc.) that is independent from the state / country-wide filtered News / Calendar stream. This means that a Chapter can coordinate its own internal projects that are separate from the rolled-up consolidated Chapter view that users will see when they are seeking information from a wider geographical area of what is going on in a larger group of Chapters than just City-level. Anyone can view a Regional Chapter's internal-Team, but can not post to their Team-page unless granted such a permission [as per any other Team/Chapter]

TODO:Further details in relationship map, interface interpolation in wireframes [Wireframe]

##ZGC-Front page Feeds (incl. Twitter) Incorporate the Blog feeds into our home page from thezeitgeistmovement.com, blog.thezeitgeistmovement.com, zeitnews.com, twitter feed from @zmglobal,

TODO: Need to define which feeds will be incorporates and then lay them out in the desired manner in the Wireframes [Wireframe]

##Chapter/Team Page customization Chapters will be able to change their logo, specify visible widgets for logged in and not logged in visitors, block locations within content areas and some control of colors of their (sub)site. Chapter can add new pages to their site and menu structure.

TODO:Need to define precisely what can be managed, then need to incorporate interface into Wireframes/Sitemap [Wireframe]

##Chapter/Team integration with External RSS feeds to auto generate their Chapter/Team content. Chapter/Teams will be able to add external RSS feeds to their dashboard and/or into their Blog to auto-generate content from a 3rd party site. Example: UK Chapter wants to include content from its existing UK Chapter blog into the ZGC during a transitional period when both the external UK Chapter site are used as well as the new ZGC Regional page.

TODO:Should be part of total available widgets. All widgets need to be defined. [Wireframe]

##Chapter/Team Recent activity Provide a feed of recent activity that is taking place within the Chapter/Team.

TODO: Need to see if standard atrium covers all recent-activity needs. We may need to define exactly what types of activity need to be tracked

##RSS Feeds integration All the different News/Blog pages on our sites [from all Chapters/Teams and also from the ZGC-Front page] need to be available as RSS feeds.

##Calendar features for anonymous users Anonymous users should be able to view public calendar events as well as share them via social media.

TODO: Define possible activities, use cases. [Wireframe]

##Mass-Special notifications For certain Roles, it should be possible to have special notification options, such as notify all other Chapter coordinators of a particular Content item change/addition/removal. Other mass notification special options might be to notify everyone on the entire site [mass-broadcast]. User's can opt-in or out of this form of mass-mailing if they do not want to get this particular kind of mass-special notification

TODO:To be incorporated in wireframes, roles and user data fields [Wireframe]

##Blog permissions If desired by the Chapter/Team: Only users with the appropriate role [example: Chapter Coordinator, Blogger] are able to create Blog entries in their Chapter/Team.

TODO:To be incorporated in roles and user data fields [Wireframe]

##Chapter/Team Forum Enable the creation of forum topics in each Chapter/Team. Users will be able to read any Forum from any Chapter, but to post in a Forum a user needs to be a member of that Chapter/Team. Certain Chapter/Teams may decide to have an open-policy, in that case, user's can be auto-approved to join that Chapter/Team and therefore also will be automatically granted the ability to post in that Chapter/Team's forum.

[Wireframe]

##Global Forum Enable a General forum on the ZGC-Front-Page that is not associated with any Chapter/Team.

TODO:To be incorporated in wireframes and sitemap. [Wireframe]

##Rate content Users should be able to vote on content. Either a 5-star or thumb up/down system in order to attribute value to various types of content. This could be Forum posts, blog posts and/or other pieces of data [TBD] that would benefit from a rating. Ratings can then be used as an additional filter/sort criteria, to better access important/relevant information.

To be incorporated in wireframes and various data-types [Wireframe]

##Social networking integration Allow users to easily share appropriate web-pages on social media. All popular social media service should be included in the integration. Add Chapter/Team Facebook buttons to allow visitors to like, share / recommend from the Chapter/Team's front-page.

##Priority Translation Queue Management Certain users (Chapter Coordinators) should be able to promote important content, needing to be shared with other chapters, into a priority-translation queue for the Linguistic Team. The Linguistic Team can then review the items which have been added to their Translation Queue for appropriate translations to occur.

TODO:To be incorporated in wireframes and various data-types [Wireframe]

##Automatic Translations Users should be able to automatically have the pages that they visit be translated into their language if that page has not already been "officially" translated by the linguistic-Team into their respective language. This automatic translation will use semi-perfect tools like Google translation, Dojo or other.

TODO:To be incorporated in wireframes. Need to define the various states: original, officially-translated, Google-translated. [Wireframe]

##Chapter subscriptions / mailing list Allow a chapter to display a sign-up widget for the chapter updates, newsletter email list, even if they are not fully registered at the website. This could be through some form of website registation, or using MailChimp or Google Chapter/Teams mailing list for management of the newsletter message.

##Polling tools & Decision making Allow users to post polls in chapters/teams to gather data or get feedback from the larger community.

TODO:To be incorporated in wireframes. May imply data-type changes.

##Sub-Groups Chapter/Teams need to be able to assign users to a specific Sub-Group. Tasks and other content can then be assigned to a specific Sub-Group and Sub-Groups can be notified as a whole of activity that takes place within their Sub-Group. There also needs to be a page that collects notices and activities related to that Sub-Group for easy overview.

TODO:Need to define how this works, interacts between Groups [if at all], how it integrates with Notifications, Sub-Group views, assignments, and various data-types.

##ZGC-Front-page Chapter/Team file/document repository There should be file/document repositories, with pre-determined tags for topic-area in Chapters/Teams and also in the ZGC-Front page. A document should be able to be promoted to be visible in more than one chapter/global if it is pertinent to several areas without duplicating the file unnecessarily in the file system. In this way media files or other important documents can be accessed from many locations and shared between Chapters/Teams/ZGC Front-page. Visibility of the document in other chapters can be determined by rating, promotion flags [set by Coordinators] or other TBD methods.

##Content inappropriate-flagging Give users the ability to flag content for review or removal in case of spam or highly offensive content. Flagged content would be un-published (when a certain threshold of negative-flags are set, number TBD; could be 1) and a message would be sent to a moderator or page admin to review it and re-enable it if mistakenly flagged. Users need to have the ability to un-flag so they can reverse a click mistake.

TODO:Need to define rule to make sure everyone agrees with flagging rule in release 1. Incorporate rule defined in wireframe.

##Online users display Display a list of users who are online site-wide, chapter, and team wide, depending on area and where this widget is available.

TODO:If the need is greater than what is currently available in Atrium we will need to define exactly what this is.

##Simple hash-tag recent tweets widget Make a recent-tweets of [selected] hash-key[term] visible in Chapter/Team dashboards as a widget.

TODO:To be defined as part of widget definitions

##Blog Allow blog-entries to be promoted to Regional or ZGC-Front-Page, based on a content ranking such as a number-of-stars system or (tbd) a promotion-flag that can be set only by users of a certain role [example: Chapter Coordinator]

TODO:Define as part of data type and wireframes

##Wiki A collaborative document creation environment for which users of a Chapter/Team can edit and format pages into an organized book/notebook structure. Version control is to be implemented for finding overwritten information or reverting to previous version if needed. Write access to wikis at the Chapter/Team level would be limited to chapter/team members only.

TODO:If the need is greater than what is currently available in Atrium we will need to define exactly what this is.

##Chapter/Team Facebook Group automatic updates Instructions for how to add your RSS feed to your Chapter/Team's Facebook Group Page (using the Facebook Application: RSSGrafiti)

##Embed photo galleries from external sites Chapter/Teams should be permited to embed photo-galleries from third-party sites.

No need: to use WYSIWYG editor