Skip to content

August Feedback #213

Description

@caviri

Hi @sabinem, I'm dropping in some of the feedback from @hanaCasey here, compiled from the last meeting with Valerio and Thibaut. Please reach out to her if you have any doubts. Apologies beforehand if some of these are already corrected in main, these screenshots are comming from the sketch branch.

Dark/Light Theme

Image

The theme should be adjusted to the system theme.

Landing Page

Image

Award-winning and Event showcase can be deactivated now.

Image

Past events shouldn't be here.

Hackathon Section Specific Changes.

In general, they found it a bit confusing to have the sidebar split in two and would consider an improvement to keep both separate. However, I don't think this is a priority right now. It's fine as long as we keep both areas strictly function-separated, so there are no edit functions on the user pages.

USERS Section

Participants

Image
  • No admin/owner actions. Just view.
  • Missing view detail page for each user.
  • Check Image URL

Proposals

Image
  • Proposals will not be used in these next hackathons.
  • Also, I'd suggest removing this from the sidebar and placing it under Projects instead.

All Projects

Image
  • Change name to Projects
  • Remove actions reserved for admin/owners
  • A user would only be able to edit a project that he/she proposed and is still pending approval.

Teams

Image
  • Teams: image URL absent. This should be defined by the hackathon organisers when generating a team. As a backup, we can take the image of the project.
  • No edition of teams here.

Timeline

Image
  • Probably this is an artefact of the sketch, but the user time should display a summary in a Markdown page that we can prepopulate with the phases timeline. However, the admin has the last word on what to include here. I can think of a quick frontend solution that arranges the values and generates an MD table. But I leave this to you.

MANAGE Section

Manage Hackathon

Image
  • Change name to General Settings
  • Remove panel of what participants can do. This control should be delegated to a manual phase setting. Capabilities should be associated with Phases.

Manage Tracks

Image
  • Probably solved already. We don't need tracks for this hackathon.

Manage Participants

Image
  • This page is absent; please add a general table view of participants containing the replies to the registration form.
  • Check the image above for inspiration.

Manage Projects

  • Similar to Manage Participants, this section was absent in the sketch. We need a table view of the projects showing all the actions the admin can take.
  • New project, Approve project, Edit project, Remove project

Manage Teams

Image
  • Teams will be arranged in a datasheet in G Drive. We need to provide a way to export the list of participants as csv, or JSON. These documents should include all required columns to configure the teams.
  • Teams can be generated from the teams column.

Manage Timeline

Image
  • We need to have a way to activate the current phase manually. If manual mode is active, deadlines are just suggestions.
Image
  • Inside each phase, we need to define a temporal range.
  • A linked page is not needed for this first hackathon. However, in the future, linked pages should be cumulative. I mean, pages linked to previous phases should remain in the sidebar.

Manage Voting

Image
  • Manage voting shouldn't contain user-specific voting messages.
  • 1 vote per category by now.
  • Voting results should be displayed here.

Manage Prizes

Image
  • Winners are defined by the admin independently of the voting.
  • Allow defining prizes and assigning a single winning team to it.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions