{"id":891933,"date":"2008-09-23T12:34:11","date_gmt":"2008-09-23T16:34:11","guid":{"rendered":"https:\/\/segue.middlebury.edu\/view\/html\/node\/891933"},"modified":"2013-09-21T17:45:05","modified_gmt":"2013-09-21T17:45:05","slug":"content","status":"publish","type":"page","link":"https:\/\/segueproject.org\/segue-documentation\/segue-v2\/documentation\/overview\/content\/","title":{"rendered":"Information Architecture"},"content":{"rendered":"\n\n\n
\n
\n

Segue’s editing UI uses AJAX to keep track of settings so pages do not have to be reloaded as much when editing.<\/p>\n

Mousing over the page in edit mode highlights relevant content and menu containers and the block and items they contain.The options for sections, pages and content blocks can be set by clicking on the options link in the upper right hand corner of the box that contains the content, page or section.<\/p>\n

Options include setting the sort order of content blocks (recent first, recent last, alphabetically…etc), displaying block author, creation date, links for discussion, history… and so.<\/p>\n

Options cascade down so that settings applied to a contain container will become the default settings for the content blocks in that container.\u00a0 That said, settings applied in content blocks can override the settings applied to the container.<\/p>\n<\/div>\n<\/td>\n

\"segue-ui2-overview02.gif\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Organization<\/h3>\n
\n
<\/div>\n\n\n\n
Segue provides various ways for individuals and institutions to develop, organize and share content including sites, sections, pages and content blocks all of which are nodes with their own unique identifiers. <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n<\/div>\n

Domains<\/h3>\n
\n

Segue can be configured to organize sites into various domains.\u00a0 This is done by categorizing placeholders, the namespace reserved for sites.\u00a0 For example, an institution may categorize course placeholders (which typically include the course code in their name) and reserve one sub-domain for these while categorizing personal sites into another sub-domain.\u00a0 Any number of categories can be used for sites in a given instance of Segue and each can be mapped to a different domain.<\/p>\n<\/div>\n

Sites<\/h3>\n
\n

Segue by default has placeholder categories for personal and class sites.\u00a0 Segue can be integrated with administrative systems to retreive course information and use this to assign placeholders.\u00a0 Thus faculty and students can see all the courses they are participating in.\u00a0 Specific users and\/or groups can be given authorization to create an unlimited number of personal sites simply by appending to their username text that will identify their site (e.g. achapin-blog).\u00a0 Sites can be also be moved from one placeholder to another.<\/p>\n<\/div>\n

Sections<\/h3>\n
\n

All Segue sites have at least one pages container where links to at least the main sections and pages of the site is contained.\u00a0 A section is simply a node in Segue that has its own page container that (currently) is viewable only when that section or pages in it are selected.<\/p>\n<\/div>\n

Pages<\/h3>\n
\n

A page in Segue is a node that has its own content container(s) that are viewable only when that page is selected.<\/p>\n<\/div>\n

Content Blocks<\/h3>\n
\n

A content block in Segue is a node in a content container that contains plugin content.\u00a0 Segue has a well-defined plugin A.P.I. that allows developers to create their own plugins for Segue.<\/p>\n

All content blocks have options to hide or show their titles, the names of their authors and\/or editors, the date they were created or updated.\u00a0 There are also options to attached a threaded discussion to a content block and provide access to version history (for content blocks that support versioning).<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Segue’s editing UI uses AJAX to keep track of settings so pages do not have to be reloaded as much when editing. Mousing over the page in edit mode highlights relevant content and menu containers and the block and items… More →<\/a><\/p>\n","protected":false},"author":29,"featured_media":0,"parent":473031,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-891933","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/891933","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=891933"}],"version-history":[{"count":9,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/891933\/revisions"}],"predecessor-version":[{"id":200001472296,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/891933\/revisions\/200001472296"}],"up":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/pages\/473031"}],"wp:attachment":[{"href":"https:\/\/segueproject.org\/segue-documentation\/wp-json\/wp\/v2\/media?parent=891933"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}