Page types

Cyco has different types of pages. Each type has a purpose. The page’s fields, permissions, and other attributes reflect that purpose

For example, course pages are, well, pages in a course. Course pages are listed in course content trees, like “Opening and closing files” from a programming course:

A course page

Course pages have page navigation bars:

Page navigation bar

Authors and administrators can edit course pages. Every else can only view them.

Blueprint pages are like course pages, but are used in course planning. Blueprints have their own content trees. One difference between course pages and blueprint pages is that students can’t view blueprint pages, their content trees, or see them in searches.

Here are the page types in Cyco:

  • Course pages. For most course content.
  • Blueprint pages. For course design.
  • Basic pages. For home pages, About Us pages, contact pages, terms of use pages, and other things that are common on Web sites, but not part of a course.
  • Exercises. Each page has one exercise.
  • Patterns. Useful ways of doing things.
  • Big ideas. Core ideas that motivate patterns, e.g., “Make code easy to understand.”
  • Badges. Awards students can earn.
  • Classes. Each class page is for a group of students learning together.
  • Class posts. Pages about something specific to one or more classes.

There are a few others that are technically page types, but conceptually are separate data objects:

  • Exercise submissions. A submission by one student for one exercise.
  • Rubric items. Criteria used to assess submissions.
  • Pseudents (pseudo-students). Virtual students who go through a cycourse alongside the real students.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Prove that you are sentient.
12 + 5 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.