CSC/ECE 517 Spring 2024 - E2435 Implement Frontend for the My Profile

Expertiza

Expertiza stands as a versatile open-source web application constructed on the robust Ruby on Rails framework. Its primary function revolves around empowering instructors to craft tailored assignments, complete with curated topic lists, providing students with ample options for selection. Moreover, the platform extends its capabilities to facilitate seamless team formation, enabling students to collaborate efficiently on assignments and larger-scale projects.

One of Expertiza's standout features lies in its support for peer review processes, a crucial aspect of modern education. Through this functionality, students can engage in constructive feedback exchanges, offering evaluations and critiques on their peers' submissions. What sets Expertiza apart is its flexibility in accommodating various document formats, including URLs and wiki pages, ensuring comprehensive assessment avenues.

In essence, Expertiza represents more than just a mere educational tool; it embodies a comprehensive solution for managing assignments, fostering teamwork, and facilitating peer evaluations. Its open-source nature further enhances accessibility, making it freely available to educational institutions and individuals alike, thereby democratizing access to quality education tools.

Overview

The My Profile page in Expertiza currently implemented in Ruby needs to be reimplemented using React and TypeScript to enhance user experience and maintainability. The reimplementation aims to maintain feature parity while improving intuitiveness and usability.

Plan for Reimplementation Details

Technologies

• React: Front-end library for building user interfaces.
• TypeScript: Adds static typing to JavaScript, enhancing code quality and maintainability.

Reimplementation in React and TypeScript

• Rewrite the Profile Controller logic in React components.
• Convert form submissions and updates to asynchronous requests using React hooks or class-based components.

Anonymized View

• Ensure the option for anonymized view is preserved in the new implementation.
• Create a toggle or checkbox to switch between anonymized and standard views.

Language

• Description: Users will be able to set their preferred language for the interface, allowing for localization to cater to a diverse user base.
• Details:
  • A dropdown menu or similar interface will enable users to select their preferred language from a list of available options.
  • The selected language will determine the language used throughout the user interface, including labels, messages, and instructions.
  • This feature enhances accessibility and inclusivity by accommodating users who prefer to interact with the application in languages other than the default.

Timezones

• Description: Users will have the ability to set their preferred timezone, ensuring that timestamps and deadlines are displayed accurately according to their local time.
• Details
  • Users can select their timezone from a dropdown menu or similar interface, choosing from a list of supported timezones.
  • The selected timezone will be used to convert timestamps and deadlines to the user's local time, providing a more accurate representation of time-sensitive information.
  • This feature improves usability and reduces confusion by presenting time-related information in a format that is familiar and relevant to the user.

Email Options

• Description: Users can customize their email notification preferences for various events such as work reviews, submissions, and meta-reviews.
• Details
  • Checkboxes or similar controls will allow users to opt-in or opt-out of email notifications for specific events.
  • Users can select the types of notifications they wish to receive, tailoring their email preferences to suit their needs and preferences.
  • This feature provides users with greater control over their communication preferences, reducing unnecessary email notifications and improving overall user satisfaction.

User Interface Enhancement

• Description: The user interface (UI) will undergo a redesign to make it more intuitive and visually appealing. The goal is to create a modern look and feel that aligns with current design trends while ensuring consistency with the existing Expertiza interface.The UI design will be homogeneous to the current reimplementation of Expertiza to maintain consistency across the platform. It will feature a clean and intuitive layout with clear navigation and easily identifiable controls.
• Details:
  • The redesign will focus on improving the layout, typography, color scheme, and overall aesthetic appeal of the user profile page.
  • Elements such as buttons, forms, and navigation will be redesigned to provide a more seamless and enjoyable user experience.
  • Homogeneity with the current reimplementation of Expertiza will be maintained to provide continuity and familiarity for existing users.

Form Handling

• Refactor the form handling logic to work seamlessly with React's state management system.
• Implement form validation and error handling to provide a smoother user experience.

Routing and Navigation

• Adjust routing and navigation to accommodate the new React components.
• Ensure proper redirection upon form submissions and updates.

Modularization and Componentization

• Break down complex functionalities into smaller, reusable components in React.
• Each component should have a single responsibility, making it easier to understand and maintain.
• Use clear and descriptive names for components, variables, and functions to convey their purpose effectively.

Consistent Coding Style

• Enforce a consistent coding style across the project using linters and code formatting tools.
• Follow established coding conventions and best practices to ensure readability and maintainability.
• Document code with comments and annotations to explain complex logic or implementation details.

Testing and Quality Assurance

• Conduct thorough testing of the reimplementation to ensure functionality and compatibility across browsers and devices.
• Address any bugs or issues discovered during testing before deploying the new version.

Design Principles to follow

Single Responsibility Principle (SRP)

• Each React component will have a single responsibility, such as displaying user information, managing language preferences, or handling email options.
• Separate concerns such as data fetching, state management, and rendering to improve modularity and maintainability.

Separation of Concerns (SoC)

• Dividing the user profile page into distinct components for different sections, such as profile information, language preferences, and email options.

Don't Repeat Yourself (DRY)

• Refactoring redundant code or logic into reusable React components, hooks, or utility functions.
• Avoiding duplicate data-fetching or state management logic across multiple components by centralizing it in shared modules.

Open/Closed Principle (OCP)

• Designing components to be open for extension by allowing for customization or configuration through props or context.
• Ensuring that components can be extended or modified without altering their core functionality by adhering to React's composition model.

Team

Mentor

• Riya Gori (rygori@ncsu.edu)

Members

• Aakarsh Satish (asatish2@ncsu.edu)
• Shubh Nisar (snisar@ncsu.edu)
• Sinchana Shetty (skshett2@ncsu.edu)