Chapter View

[WillieCubed]

Overview

Being able to create entries in Guide is essential, but we should have some way of organizing them. If we consider the guide as a handbook, it makes sense to have "chapters" to group related content that's thematically similar. For example, Guide could have a chapter focused on getting more involved on campus, which may include entries like "Finding a Club for You", "Finding Research on Campus", or "Handling Mental Health".

In the future, a chapter can contain a set of milestones or goals (to-dos) related to the chapter content that a user can mark as completed.

Implementation Proposal

• Each chapter has one or more GuideEntry objects associated with it.
• Each chapter has a unique chapterId that identifies it.
• Each chapter is accessible by URL with route /chapters/[chapterId].
• Each chapter must have a title.
• Each chapter must have content with the same schema or data type as a GuideEntry.
• When rendered, a chapter must display all of its associated entries.
• Each entry displayed on a chapter (page) should link to the respective entry page (e.g. /entry/[entryId]).
• A user with permission to create or update chapters should be able to change the GuideEntry objects associated with it.