Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

The "Explore" area is designed to be an interface where students can engage with educational content across various subjects.

User Story

As a student, I want to be able to filter the educational subjects that appear on my "Explore" dashboard, so that I can focus on content that is most relevant and interesting to me.

Figma

https://www.figma.com/file/2P8kwFEVvVNOVzG4D2E5Sj/Student-UI?type=design&node-id=6%3A2366&mode=design&t=F23GTnmedOZYdSH5-1

Epic

Epic 193777: Student Center

UI Description

  1. Search Bar

    • Search functionality will be by titles, phrases, keywords, and tags of the content.

    • Content displayed as user searches should be content in the student's grade level or grade band (3-5), (6-8), (9-12).

  2. Subject Filters

    • Each subject that has content will display a subject selection filter below the search bar.

    • Subject selection filters will automatically be pre-selected when the user navigates to the Explore page

    • De-selected subject selection filter will hide the content for that given subject.

    • Subjects: Social and Emotional, Mental Health

  3. Recommended For You Section

    • The recommended for you section will change as the user selects and interacts with content.

    • Recommended For You Section will show the user content that is similar to the content they have previously selected and interacted with on the platform.

  4. Content Sections

    • Each content section shall have a header (subject title) and a series of content cards.

  5. Content Cards

    • Content cards will display a thumbnail, the subject, and the title of the content.

    • Thumbnail: Thumbnail images must occupy 100% of the container width and align to the top of the container.

  6. Browsing Functionality

    • The interface will include navigation arrows within each content section for content browsing.

User Interaction and Validation Notes

  • Subject Selection:

    • Each subject header will have a selection toggle to enable or disable the selection.

    • When a student deselects a subject, the corresponding content section should smoothly transition out of view.

    • The state of selected/deselected subjects will be saved for the user's next session.

  • Content Navigation:

    • Clicking the arrow icons will shift the content cards within that section.

    • The card on the far right will transition to the far-left position, appearing as the first card.

    • The transition should be animated smoothly to convey the cycling of content.

  • Validation:

    • Ensure that deselected subjects remain hidden across sessions unless re-selected by the user.

    • Validate that the content cycling functionality correctly cycles the cards without skipping any content.

    • User selections and interactions should be responsive with no lag to promote a seamless user experience.

Workflow Description

  1. Initial Load:

    • When a student enters the "Explore" area, they are presented with a dashboard populated with subject sections based on the default or previously saved preferences.

  2. Customizing Content View:

    • The student reviews the subjects and decides to select or deselect which content is displayed.

    • They toggle off subjects that they are not interested in, which immediately removes the corresponding sections from the view.

  3. Navigating Content:

    • Within a content section, the student clicks the navigation arrow to explore more content cards.

    • The cards animate to the left, and the card from the right becomes the first on the left.

  4. Session End:

    • When the student leaves the "Explore" area, their subject selections and the position of the content cards within each section are saved.

    • Upon return, the student finds the "Explore" dashboard as they left it, allowing them to pick up where they left off.

  5. Younger and Older Student Versions

    • We need to support the younger student and older student versions of the Student Center. In the future, the younger and older student centers will have different features.

    • The updated Student Center UI described in the requirements and designs are the same for the younger and older student centers. We should maintain the separation of the younger student and old student versions so that they can have different features in the future.

  • No labels