{"id":1475668,"date":"2008-12-09T21:59:31","date_gmt":"2008-12-09T21:59:31","guid":{"rendered":"https:\/\/segue.middlebury.edu\/view\/html\/node\/1475668"},"modified":"2012-08-06T20:32:44","modified_gmt":"2012-08-06T20:32:44","slug":"sites","status":"publish","type":"page","link":"https:\/\/segueproject.org\/curricular-technologies-report\/differentiation\/sites\/","title":{"rendered":"Sites"},"content":{"rendered":"

Sites Management<\/h3>\n
\n

\"\"Most web content management systems were designed to allow for the creation of primarily one site and secondary multiple sites.  This is certainly the case with Drupal<\/a> and MediaWiki<\/a>.  In 2004, WordPress MU<\/a> (multi-user) was introduced which enabled the creation of many more blogs from a single instance of WordPress. Confluence<\/a> has a concept of "spaces" which can contain content that is accessible to a specified group of users.  Like others systems that manage course sites, Segue was specifically designed to allow for the creation of many sites from a single instance. It is in the managing of content and namespaces across multiple sites where Segue has some distinguishing features.<\/p>\n

Copy and Paste<\/i>
\nSegue sites can be copied and pasted into new locations in Segue much like files can be copied and pasted in computer operating systems.  When pasting a site, users can chose to paste a copy of the site or move the entire site to a new placeholder.  In the same way, site sections, pages and content blocks can be also be copied and then pasted to a new location in the same site or any other site in an instance of Segue that the given user has permission to add to.  Segue v2 introduces a simple and efficient user interface (UI) for accomplishing this allowing users to copy multiple sites, sections, pages and content blocks to a "selection" and then pasting any subset of the selection to new location(s).  Most other applications accomplish similar functionality by exporting entire sites or selected portions of site to files and then importing those files into new sites. Segue’s copy\/paste implementation allows the system to maintain un-tamperable attribution and history even as elements are copy\/pasted to new locations.<\/p>\n

Namespace<\/i>
\nWhen Segue is used to manage courses and integrated with a student information systems, it will generate placeholders for course sites and give course instructors permission to create sites like most course management systems.  Segue also has some additional options for managing the namespace for sites.  Sites can be categorized into types and these types can be mapped to different domain names.  For example at Middlebury, personal sites can mapped to seguecommunity whereas all other sites are mapped to segue.  By default, Segue allows users to create as many personal sites as they want.  The namespace for these sites are managed simply by prefixing whatever name users chose for their site with their Segue username.  This sitename prefix pattern used for personal sites could also be extended to departments.  Thus a group of users could be given permission to create sites whose names are prefixed with "lis-"  WordPress MU can be set up to allow any authenticated user to create a blog, but does not provide any constraints on names they chose. <\/p>\n

Templates
\n<\/i>Most content management systems use templates to define the layout and appearance of sites. Templates in Segue are simply site starting-points, XML representations of sites that are used to create new sites.  Segue administrators can make any site a template.  Segue users can choose any template as the starting point for their new site.  Since Segue templates can include not only layout and display specifications but also content, it is possible to allow users to create sites that already have content such as a particular information architecture (e.g. sections and pages useful for creating an e-portfolio) or already have a particular layout settings (e.g. content containers configured to function as a blog or wiki).  Most other content management systems such as WordPress, Drupal, Confluence simply allow users to chose a theme and possibly a format for their new site and then provide a "empty" instance.\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Sites Management Most web content management systems were designed to allow for the creation of primarily one site and secondary multiple sites.  This is certainly the case with Drupal and MediaWiki.  In 2004, WordPress MU (multi-user) was introduced which enabled … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":29,"featured_media":0,"parent":1441745,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1475668","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/pages\/1475668","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/comments?post=1475668"}],"version-history":[{"count":2,"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/pages\/1475668\/revisions"}],"predecessor-version":[{"id":1515952,"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/pages\/1475668\/revisions\/1515952"}],"up":[{"embeddable":true,"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/pages\/1441745"}],"wp:attachment":[{"href":"https:\/\/segueproject.org\/curricular-technologies-report\/wp-json\/wp\/v2\/media?parent=1475668"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}