code-institute-community / ci-hackathon-app Goto Github PK

Depends on #M10. Update Hackathon and Profile model with new fields.

This applies for user_type staff as well.

Create a new page to display the detailed information about a hackathon when clicking on the "Read More" link on the "View Hackathons" page.

• Once an admin triggers the event to distribute teams/judges:
  • Number of teams and participants per team should depend on total number of participants.
  • This should assign a random Judge/Mentor to each team as well.
  • To ensure a balanced range of skill levels in each team, the distribution algorithm should assign participants to teams based on their experience (LMS Module) ie. divvy out all Alumni first (if any), then MS4, MS3, MS2, MS1.
  • The aim is to have between 4-7 participants per team ideally.

Editable profile details should include:

• First Name
• Last Name
• Email Address
• Slack Display Name
• Current Module on LMS
  • dropdown options
  • includes option for alumni
• Shipping Address
  • hidden by default
  • is enabled only if part of a winning team

All users should have ability to logout as is customary User Experience.

@JimLynx
Adding initial content and layout for footer so that it can be styled accordingly.
Links can be adapted to whatever content (Privacy Policy, FAQ etc) is included in the footer later

As a developer, the environmental setup on a local IDE is not as straightforward as first anticipated.

In my case, I:

• Opened VSCode

• Cloned the forked repository

• Created the .env file

• Ran the python -m venv .venv command, and although the .venv folder was created, virtual environment was not initialised

Resolve:
A way to automate this process with all of the correct commands in sequence would be excellent.

@Eventyret

Registration should include the following details:

• First Name
• Last Name
• Email Address
• Password
• Slack Display Name
• Current Module on LMS
  • dropdown options
  • includes option for alumni
• Registration Code
  • provided by CI
  • changes with each Hackathon

• Registration should include the following details:
  • First Name
  • Last Name
  • Email Address
  • Password
  • Slack Display Name
  • Registration Code
    • changes with each Hackathon

• In lieu of #A05 (the manual event for distribution), this would be automated 48hrs prior to the official start date/time of the Hackathon:
  • Number of teams and participants per team should depend on total number of participants.
  • This should assign a random Judge/Mentor to each team as well.
  • To ensure a balanced range of skill levels in each team, the distribution algorithm should assign participants to teams based on their experience (LMS Module) ie. divvy out all Alumni first (if any), then MS4, MS3, MS2, MS1.
  • The aim is to have between 4-7 participants per team ideally.

SEE WIKI FOR MORE INFO
https://github.com/Code-Institute-Community/ci-hackathon-app/wiki/User-Stories#miscellaneous-user-stories

This is an issue for multiple PRs.

Please tag yourself and say which templates you will be working on!

Submissions should include:

• Team Name
• Name of Team Speaker during presentations
• Link to Source Code / Repository
• Link to Deployed Site
• Consent option to share deployed site on CI social media

@JimLynx

Register & Login Forms require styling

Expected Behavior

Styling to keep consistent with the current UX

Current Behavior

Forms are squished to the left and rather unsightly

Possible Solution

CSS 🥇

Database Models to be created:

• HackAwardCategory
• Hackathon
• HackTeam
• HackProject
• HackProjectScore
• HackProjectScoreCategory

Model Schema can be found on the Development Wiki

@Ri-Dearg

Participants should have the ability to access their personal profile page once they've successfully registered and logged in.

To help with development, it would be great to have a bunch of test data.
This would allow developers to loaddata or fixtures from a JSON file perhaps.
It could contain a bunch of sample users and hackathon events.

It should be possible to generate them from the admin panel initially, and then perform a dumpdata command to generate them into a JSON file.

For example, let's assume you have created some test users (of various types - staff, admin, participants, etc), and some sample hackathon events. You therefore should be able to dumpdata as such:

python3 manage.py dumpdata profiles > profiles.json
and
python3 manage.py dumpdata hackathon > hackathon.json

In theory, this would generate the data from the admin panel, directly into the JSON file, so any other developer/contributor can simply loaddata and have some sample data already loaded.

Further information from the Django Docs:
https://docs.djangoproject.com/en/3.1/ref/django-admin/#dumpdata

• Only available until the teams/judges are dispersed automatically.

• Only available until the teams/judges are dispersed automatically.

• Editable profile details should include:
  • First Name
  • Last Name
  • Email Address
  • Slack Display Name

• Enables profile editable field.

I would like to be assigned to the design of the user profile page/area.

Hackathon:
- org (default: CodeInstitute)
- status (draft/published/deleted; default: draft)

User:

• org (default: CodeInstitute)

All user types should have the ability to Login via Login template and form and be redirected to landing page with message of success.

In the event the user has not Registered promote Flash Message features to detail to user of same.

• Once all Judges have submitted their scores, an automatic tally of scores should determine the winning team.
• This should also trigger the winning team's profile to allow them to update their shipping address.

• Visible items should only include:
  • Team Name
  • Slack Display Names of Members

• Becomes available only after a Hackathon End Date/Time
• Judging per team using the standard criteria:
  • Presentation and Adherence to Theme (1-15 dropdown score)
  • Team Collaboration (1-15 dropdown score)
  • Usability and Practicality (1-10 dropdown score)
  • Effective User of Course Knowledge (1-10 dropdown score)
  • Awesomeness (1-10 dropdown score)
• Cannot edit scores once submitted

Depends on #M10. Update Hackathon and Profile model with new fields.

This applies for user_type staff as well.

@JimLynx
After running setup.bat, the script injects SITE_NAME as "localhost", which does not run on local IDE

• Hackathon Name
• Hackathon Start Date/Time
• Hackathon End Date/Time
• Hackathon Theme
• Hackathon Description

Landing page - created bootstrap accordion and carrousel blocks on landing page. positioned next to each other and made sure they are responsive. used orange color and black font to improve color contrast

Also check with html and css validators and got all good.The page lacks content, which will be added later. Question: how can i add content?

Visible items should only include:

• Team Name
• Slack Display Names of Members

• This is so we know where to send prizes to winning teams.

• This should eventually be automatic once an Admin triggers an event to divide participants into teams.

• Hackathon Name
• Hackathon Start Date/Time
• Hackathon End Date/Time
• Hackathon Theme
• Hackathon Description
• Org
• Status

@JimLynx