GAC Website Beta Demo 18 April 2017 What are we
Description: GAC Website Beta Demo 18 April 2017 What are we trying to accomplish Setting some achievable objectives Our Progress Demonstration Launch Plan Agenda 2 Slide Recapping some history In December 2014, the GAC ACIG published a report reviewing
Related Topics
Download Presentation
"GAC Website Beta Demo 18 April 2017 What are we" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
slide1. GAC Website Beta Demo 18 April 2017<br>
slide2. What are we trying to accomplish
Setting some achievable objectives
Our Progress
Demonstration
Launch Plan Agenda 2 Slide<br>
slide3. Recapping some history In December 2014, the GAC ACIG published a report reviewing the existing GAC Website (Wiki). Some key findings included: Website was on an outdated technology platform
Few GAC Members were making use of the collaborative features
Commenting, Form Submission, Document Revisioning, etc.
Organization of information was not very clear (i.e. key source of documents is the GAC email list)<br>
slide4. Move GAC Website to new platform Reorganize structure of content Build repeatable templates for creation of content Begin effort to improve findability of content Begin effort to enable holistic translation support Move toward ongoing and continuous support and assistance from ICANN Staff 1 2 3 4 5 6 Setting some achievable objectives Together with ICANN staff, a GAC TTF set out to achieve the following objectives with the new GAC Website<br>
slide5. Our Progress against our objectives New Platform: dotCMS as a content management system
more robust than previous wiki at managing and organizing content
Improved ability to style and present content to site visitors
Restructure Content: New site architecture that highlights more important content (e.g., News, About the GAC, GAC Advice, Meetings & Record, Work Efforts)
Templates: Admins have repeatable forms and content management tools to build the most important content in the same format over and over (e.g., Operating Principles, Outgoing Correspondences, Communiques, Advice, Working Groups, Activities/Workstreams, etc.)
Findability: More customizable search tools enhanced by more thoroughly tagged data filters (taxonomy, start date, end date, content type, file type, etc.)
Translation Support: Throughout site content is being enabled for translation support (e.g., navigation, page titles, metadata, documents)
Continuous Support: building a website should be an evolution; to that end ICANN staff intends to put in place a continuous maintenance team to help prioritize and implement needed changes to the GAC website as necessary. In addition, as ecosystem features are develop, GAC website integrations will be included in the prioritization (e.g., Board Advice Tracking integration with Advice)<br>
slide6. Beta Website Demonstration
By: Jeff Salem<br>
slide2. What are we trying to accomplish
Setting some achievable objectives
Our Progress
Demonstration
Launch Plan Agenda 2 Slide<br>
slide3. Recapping some history In December 2014, the GAC ACIG published a report reviewing the existing GAC Website (Wiki). Some key findings included: Website was on an outdated technology platform
Few GAC Members were making use of the collaborative features
Commenting, Form Submission, Document Revisioning, etc.
Organization of information was not very clear (i.e. key source of documents is the GAC email list)<br>
slide4. Move GAC Website to new platform Reorganize structure of content Build repeatable templates for creation of content Begin effort to improve findability of content Begin effort to enable holistic translation support Move toward ongoing and continuous support and assistance from ICANN Staff 1 2 3 4 5 6 Setting some achievable objectives Together with ICANN staff, a GAC TTF set out to achieve the following objectives with the new GAC Website<br>
slide5. Our Progress against our objectives New Platform: dotCMS as a content management system
more robust than previous wiki at managing and organizing content
Improved ability to style and present content to site visitors
Restructure Content: New site architecture that highlights more important content (e.g., News, About the GAC, GAC Advice, Meetings & Record, Work Efforts)
Templates: Admins have repeatable forms and content management tools to build the most important content in the same format over and over (e.g., Operating Principles, Outgoing Correspondences, Communiques, Advice, Working Groups, Activities/Workstreams, etc.)
Findability: More customizable search tools enhanced by more thoroughly tagged data filters (taxonomy, start date, end date, content type, file type, etc.)
Translation Support: Throughout site content is being enabled for translation support (e.g., navigation, page titles, metadata, documents)
Continuous Support: building a website should be an evolution; to that end ICANN staff intends to put in place a continuous maintenance team to help prioritize and implement needed changes to the GAC website as necessary. In addition, as ecosystem features are develop, GAC website integrations will be included in the prioritization (e.g., Board Advice Tracking integration with Advice)<br>
slide6. Beta Website Demonstration
By: Jeff Salem<br>