Skip to content

Content Pages

Problems teach by doing; content pages teach by reading. A page is a Markdown document that lives inside a course, ordered among the problems in the sidebar — use them for theory, week introductions, setup instructions, or anything students should read before coding.

Students open a page at /page/<page-id>; it renders as a document with a table of contents.

The index page

The page named index is special: it's the course overview, shown at the course's own URL (/c/<course-id>) instead of being listed in the sidebar. No index page → the course shows its plain name and description.

Creating and editing

  • Ask the assistant — "add a page explaining recursion to Algorithms 101" — it can read, write, and delete pages, including the overview.
  • By hand — maintainers see an edit option when right-clicking a page in the course sidebar, and the course overview has its own edit entry. The editor is the same Monaco + live-preview combo as problem files; Ctrl+S saves.

Ordering

Pages and problems share one order number that determines their position in the course sidebar. Set a problem's order on its manage page (or via the assistant); pages get theirs when written.

Tips

  • One page per concept beats one mega-page — students find things back faster.
  • Put a page before the problems that need it; the sidebar order is the reading order.
  • The overview (index) is your course's front door: what it covers, how it's graded, where to start.