{"id":469128,"date":"2008-06-25T19:35:52","date_gmt":"2008-06-25T23:35:52","guid":{"rendered":"https:\/\/segue.middlebury.edu\/view\/html\/node\/469128"},"modified":"2008-06-25T19:35:52","modified_gmt":"2008-06-25T23:35:52","slug":"overview","status":"publish","type":"page","link":"https:\/\/segueproject.org\/segue-documentation\/segue-v1\/overview\/","title":{"rendered":"Overview"},"content":{"rendered":"

Introduction<\/h3>\n
\n

Segue<\/span> is an
\nopen source content management system designed for e-learning that
\ncombines the ease of use of course management systems with the
\nflexibility of weblogs for creating various types of sites including
\ncourse, news, journal, peer review and e-portfolio. When integrated
\ninto an institution’s administrative systems, it can become a portal
\nproviding access to an indivual user’s course and personal websites.<\/p>\n

This
\noverview introduces many of the features of Segue. Within feature
\ndescriptions are step by step instructions for how to use features.
\nSegue also has contextual help with its user interface.<\/p>\n<\/div>\n

Help Documentation<\/h3>\n
\n
\n
\n\t\tdownload
\n\t\t\tDownload<\/strong><\/a>
\n\t\t(101.06 kB)<\/span>\n\t<\/div>\n
\n\t
\n\t\t\"Download
\n\t<\/a>\n<\/div>\n
\n<\/div>\n<\/div>\n
This is a pdf version of the Segue help documentation contained in this site.<\/div>\n<\/div>\n

Untitled<\/h3>\n
\n

<\/span><a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23493&action=site”>Site Creation<\/a>
\nNew Sites and Users<\/span>
\nBy default, every Segue user is given a "slot" that they can use to
\ncreate a personal site. In addition, Segue administrators can create
\nany number of additional "slots" which can be assigned to any Segue
\nuser and used for any purpose. Screenshot I shows the user interface
\n(UI) for accessing personal site, other sites, as well as "slot" from
\nwhich a site can be created. <\/p>\n

Access & Activation<\/span>
\nUsers can specify who can view a given site and when it is available
\nfor viewing. In addition they can chose hide their site at any
\ntime. Site owners can refine access to further through Segue’s
\ngranular <a href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23685&action=site”>roles and permissions<\/a>.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23686&action=site”>Organization<\/a>
Hierarchical<\/span>
\nThe current version of Segue supports a three level navigational structure. This
\nmeans that a given site can be organized into sections<\/span> each of
\nwhich can contain any number of pages<\/span>. Pages in turn can contain any
\nnumber of independent timestamped content blocks<\/span> (text, images, file
\ndownloads) or can be content themselves. The content blocks of any given page can be sorted by recent first or
\nrecent last, or can be sorted by user’s who added or edited them,
\nsorted alphabetically or sorted by some custom ordering (see: Features > Weblogs<\/a>).<\/p>\n

Segue
\nsections and pages are mapped to a navigational layout to provide a
\nclear and consistent context. All sections of a site can be displayed
\nhorizontally across the top and bottom of a site or vertically in the
\nleft sidebar. Segue pages can be displayed in either the left or right sidebar<\/a> of the site and can be content themselves or RSS feeds<\/a> or dynamic lists of site categories<\/a> or participants<\/a>
\nor containers for other content blocks. If the site’s sections are
\ndisplayed in the left sidebar, then the pages of any given section
\nappear directly below the section to which they belong.<\/p>\n

Associative<\/span>
In addition to hierarchical organization of content, Segue also allows
\ncreators (and editors) to organize content into multiple categories<\/a>
\nwhich can then be aggregated. This allows creators to make associations
\nbetween content across hierarchically organized sections and pages.<\/p>\n

Reorganization<\/span>
\nAll content in Segue can be moved or copied to different nodes in the
\nsite hierarchy or to nodes in any other site. Authorization to do so is
\ndetermined by any given user’s roles and permission.<\/p>\n

RSS<\/a>
\nSegue supports both publishing its own content via RSS (really simple
\nsyndication) as well as reading RSS feeds from itself and other sites.<\/p>\n

Tagging<\/a>
\nSegue allows creators to put any given content block into multiple categories via a user interface that is modelled on del.icio.us<\/a>.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23506&action=site”>Blogging<\/a>
\nAny page of any site in Segue can be set up to function as a weblog. A
\ngiven Segue site can have dozens of separate weblogs since a Segue page
\ncan consist of any number of independent, timestamped content blocks
\n(text, images, file downloads), each of which can be made the subject
\nof a discussion or assessment. These content blocks can be sorted by
\nrecent first or recent last, or can be sorted by user’s who added or
\nedited them, sorted alphabetically or sorted by some custom ordering.
\nAs well these content blocks can be copied or moved to any other
\nlocation in the site or any other site a user has permission to add to.<\/p>\n

Podcasting<\/a>
Segue supports RSS 2.0 with enclosures. Podcasts can be created simply by uploading media files into File for Download<\/span> content blocks. Whatever text is attached to the content block becomes the RSS item description.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23494&action=site”>Course Management<\/a>
\nWhen Segue integrated into an institution’s administrative systems, it
\ncan become a portal providing access to an individual user’s course and
\npersonal websites.<\/p>\n

Customization and Collaboration<\/span>
\nSegue can be distinguished from many other course management systems in
\nthe degree to which its appearance and organization can be customized
\nand the extent to which students can contribute to the course site
\nitself.<\/p>\n

When a site is created, users can customize its appearance by chosing
\n<a href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23687&action=site”>themes<\/a> and theme settings and adding custom headers and footers. In
\naddition, users can chose from various <a href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23687&action=site”>templates<\/a> that suggest
\norganizational schema for various types of content. Once created, the
\norganization of the site can be further customized. Faculty can give
\nstudents in their classes permission to discuss, add, edit or delete
\nfrom the entire class site or any content block, page, section of the
\nsite.<\/p>\n

Faculty<\/span>
\nFaculty will see a list of all the classes they are teaching with the
\noption to create a site for any class. If classes have more than one
\nsection, a single site can be made which groups all of these sections
\ntogether into one site. Faculty can copy a course site from a previous
\nsemester into a "slot" for current semester. <\/p>\n

Students<\/span>
\nStudents will see a list of all the classes they are enrolled in with
\nlinks to sites created in Segue. As well Segue will list all the
\ncourse sites for which a given student has editor permissions.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=22633&action=site”>Discussion & Assessment<\/a>
\nDiscussions\/comments can be attached to any\/all content blocks of
\nSegue. The site owner can specify precisely who can participant in
\nthese discussions. In discussion mode, all participants can read
\nand respond to each other’s posts. In assessment mode,
\nparticipants will not be able to read each other’s posts, they will see
\nonly their own posts and replies to their post by the site owner.
\nSite owners can rate any\/all posts to a discussion\/assessment.
\nDiscussion posts can be sorted by recent first, recent last, rating or
\nauthor.<\/p>\n

Site owners have an interface available to them that summarizes all the
\nposts by all participants in a given discussion on a site or all the
\ndiscussions of a given site. From this interface, site owners can email
\nas a group any subset of discussion\/assessment participants.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23685&action=site”>Roles & Permissions<\/a>
\nSegue has a granular, hierarchical permissions structure (that matches
\na site’s organization structure) that allows site owners to precisely
\ndefine who can discuss, view, add, edit and\/or delete any content
\nblock, page or section of their site(s). <\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23687&action=site”>Themes & Templates<\/a>
\nThe appearance of any Segue site can be customized by means of themes
\nand theme settings. Each theme can have its own theme settings or
\nvariations. When a user creates a Segue site, they also chose from any
\nnumber of templates. Templates are Segue sites with various
\norganizational schema to help new users get started. Once a site is
\ncreated with a certain template, the sections, pages and content blocks
\nof the template can be modified and adapted to the user’s preference.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=22635&action=site”>HTML editor<\/a>
\nSegue has a cross-platform HTML editor (HTMLarea) that works with Win\/Mac Mozilla 1.3 or greater and Windows Internet Explorer.<\/p>\n

<a style="font-weight: bold;" href="https:\/\/segue.middlebury.edu\/view\/html\/site\/segue\/?&site=site ?<\/a>&section=5736&page=23689&action=site”>Administration<\/a>
\nAny number of users can be designated as administrators. All
\nadministrators can add\/edit users, classes and slots.
\nAdministrators can also view logs and act as any other users.<\/p>\n

Users<\/span>
\nAdministrators can add and edit users. When users are added to
\nthe Segue user database, they are sent a email with their username and
\npassword. After initial log in, users can change their password.
\nSegue can also be configured to use multiple external authentication
\nmethods. <\/p>\n

Slots<\/span>
\nAll Segue users are automatically given a "slot" to create a personal
\nsite. Administrators can create any number of additional slots
\nfor any given user.<\/p>\n

Classes<\/span>
\nAdministrators can add class "slots" to Segue and specify the
\ninstructor (as owner) and add students to the class. If Segue is
\nconfigured to authenticate with LDAP and if the LDAP server specifies
\nclass information for all users, then class slots are populated
\nautomatically when users log in. <\/p>\n

Logs<\/span>
\nAdministrators can view logs of all Segue activity. Perhaps the
\nmost useful log view for daily monitoring is by recently updated
\nsites. Logs can also be filtered by type of activity, site and\/or
\nuser and sorted in various ways. <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Introduction Segue is an open source content management system designed for e-learning that combines the ease of use of course management systems with the flexibility of weblogs for creating various types of sites including course, news, journal, peer review and… More →<\/a><\/p>\n","protected":false},"author":29,"featured_media":0,"parent":469007,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-469128","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/469128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/comments?post=469128"}],"version-history":[{"count":0,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/469128\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/469007"}],"wp:attachment":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/media?parent=469128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}