Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Campus Chapter Redesign Challenge (UI/UX) #3

Open
bijomathewjose opened this issue Aug 24, 2024 · 1 comment
Open

Campus Chapter Redesign Challenge (UI/UX) #3

bijomathewjose opened this issue Aug 24, 2024 · 1 comment
Assignees

Comments

@bijomathewjose
Copy link

bijomathewjose commented Aug 24, 2024


🎨 UI/UX Redesign Challenge [Open to All]

🌐 Campus Chapter Page

🎯 Objective

Redesign the "Campus Chapters" page on the mulearn.org website according to the new brand guidelines. The redesign should enhance user engagement, improve the visual hierarchy, and streamline the user journey on the website. Participants can submit a full UX case study with wireframes or focus on UI design with a flow.

📝 Challenge Brief

1. 🔍 Analyze the Existing Design

  • Review the current website page.
  • Identify pain points or areas where the user experience could be improved (e.g., readability, touch targets).

2. 🎨 Redesign the UI/UX according to new brand guidelines

  • 📐 Visual Hierarchy: Reorganize the content to create a clear visual flow on the website. Use typography, color, and spacing to emphasize key sections.
  • 🧭 User Journey: Simplify the process of understanding and applying for a µLearn Chaptership, ensuring that the steps are easy to follow on the website.
  • 🖱️ Interactive Elements: Consider introducing interactive elements, such as swipe gestures, collapsible sections, or touch-friendly buttons.
  • 🔗 Focus on Core Content: The redesign should exclude the navigation header and footer, allowing you to concentrate solely on the page's core content.
  • 🎨 Brand Consistency: Rebrand the overall website to the new brand guidelines of µLearn.

3. 🛠️ Design Options

  • Option 1: UX Case Study

    • 📐 Wireframes: required Create low-fidelity wireframes that outline the structure and flow of the redesigned page.
    • 📝 Design Rationale: optional Provide a brief case study explaining your design choices, user research, and how the redesign improves the user experience.
  • Option 2: UI Design with Flow

    • 🎨 High-Fidelity Mockups: required Present the final design with at least a mobile-first approach, featuring detailed visual elements.
    • 🔄 User Flow: optional Illustrate the flow of interactions on the website, highlighting key touchpoints.
    • 🎮 Prototype: optional Share an interactive prototype to demonstrate user interactions.

📅 Submission Guidelines

  • 🛠️ Tools: Use Figma for UI and UX
  • 📎 Format: Submit the Figma link with read access
  • ⏰ Deadline: September 22, 2024
  • 🔖 muId: Should include the muId of the participants.

🚀 How to Submit

  • 🔖 Comment in the issue ticket in the following format:

  • Example (replace muId with your actual ID):

- muid : [muId](https://app.mulearn.org/profile/muId)  
- link : [link](Insert Figma link inside the brackets)

🎯 Evaluation Criteria

  • 📱 Basic Screen Sizes: How well does the design scale to different screen sizes? Does the design include mobile, tablet, and desktop-based designs?
  • 👥 User-Centered Design: How well does the design cater to the needs of the target audience?
  • 💡 Creativity: How innovative is the redesign? Does it introduce any new ideas or features?
  • ⚙️ Functionality: Does the design simplify the user journey and make information more accessible on the website?
  • 🎨 Aesthetic Appeal: How visually appealing is the redesign? Does it align with the brand’s identity?

🏆 Challenge Reward

  • The reward will be based on the design evaluation.

📚 Additional Resources

📢 Additional Info

  • Resolve doubts by using the @Webwise tag in the mulearn discord lobby channel.
  • Daily office hours around IST 8:30 pm to 9:30 pm to mentor and resolve doubts in the lobby voice channel.
  • Note: Mulearn profile should be public to participate.

@Janukrishna007
Copy link

Janukrishna007 commented Aug 26, 2024

The doubts to the given issue can be discussed in the lobby channel with the tag @projectoperator so that any person in the tam of 8 members whoever is online will be able to address the issue immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants