Difference between revisions of "CLIO Guides"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__FORCETOC__ | |||
==Overview== | ==Overview== | ||
Non-profit and cultural heritage professionals often wear many hats and balance numerous responsibilities. Some are educators, some are designers, and some are developers. Many professionals are more than one. In order to help you make sense of the documentation, we've broken them down into guides for different needs. | Non-profit and cultural heritage professionals often wear many hats and balance numerous responsibilities. Some are educators, some are designers, and some are developers. Many professionals are more than one. In order to help you make sense of the documentation, we've broken them down into guides for different needs. | ||
| Line 8: | Line 8: | ||
Administrators manage CLIO Interactives and provide a decisive cohesion to the project by defining Audiences, organizing Programs and choosing what information is made available to Facilitators. | Administrators manage CLIO Interactives and provide a decisive cohesion to the project by defining Audiences, organizing Programs and choosing what information is made available to Facilitators. | ||
{{See|CLIO Administrator Guide}} | {{See|CLIO Administrator Guide}} | ||
===Educator=== | ===Educator=== | ||
Educators create the language and select the media that go into the activities for their audience. | Educators create the language and select the media that go into the activities for their audience. | ||
{{See|CLIO Educator Guide}} | {{See|CLIO Educator Guide}} | ||
===Designer=== | ===Designer=== | ||
Designers alter the look and feel of the CLIO application to better integrate it into your institution's design aesthetic and corporate branding. | Designers alter the look and feel of the CLIO application to better integrate it into your institution's design aesthetic and corporate branding. | ||
{{See|CLIO Designer Guide}} | {{See|CLIO Designer Guide}} | ||
===Developer=== | ===Developer=== | ||
Developers code the CLIO Programs and Activities, create or modify Activity types, and provide insights into technology integration. | Developers code the CLIO Programs and Activities, create or modify Activity types, and provide insights into technology integration. | ||
{{See|CLIO Developer Guide}} | {{See|CLIO Developer Guide}} | ||
=== Facilitator === | |||
Facilitators set up CLIO kiosks and get them working as part of an exhibit or event. | |||
{{See|CLIO Facilitator Guide}} | |||
=== Visitor === | === Visitor === | ||
Visitors use the exhibit and activities created for CLIO as part of their interactive experience. | Visitors use the exhibit and activities created for CLIO as part of their interactive experience. | ||
{{See|CLIO Visitor Guide}} | {{See|CLIO Visitor Guide}} | ||
Latest revision as of 14:34, 24 March 2023
Overview
Non-profit and cultural heritage professionals often wear many hats and balance numerous responsibilities. Some are educators, some are designers, and some are developers. Many professionals are more than one. In order to help you make sense of the documentation, we've broken them down into guides for different needs.
Institutional Guides
Administrator
Administrators manage CLIO Interactives and provide a decisive cohesion to the project by defining Audiences, organizing Programs and choosing what information is made available to Facilitators.
Educator
Educators create the language and select the media that go into the activities for their audience.
Designer
Designers alter the look and feel of the CLIO application to better integrate it into your institution's design aesthetic and corporate branding.
Developer
Developers code the CLIO Programs and Activities, create or modify Activity types, and provide insights into technology integration.
Facilitator
Facilitators set up CLIO kiosks and get them working as part of an exhibit or event.
Visitor
Visitors use the exhibit and activities created for CLIO as part of their interactive experience.
