Challenge Overview
Basic requirements for this challenge:
Challenge Overview
Hoherberg Ski School web application need build using ASP.Net MVC Core with focus on desktop resolution only. For this challenge we need you updates issues on Web API and the frontend.
Let's discuss any questions you have. See you in the challenge forum!
Technology Stack
ASP.Net MVC Core
HTML5
CSS3
Javascript
Jquery
Deployment environment requirements
localhost
live site
Challenge Assets:
Post your gitlab username on challenge forum to get access to our repo
- Frontend repo: https://gitlab.com/alta-ski/frontend
- Backend repo: https://gitlab.com/alta-ski/backend
Demo site:
http://ec2-3-208-93-68.compute-1.amazonaws.com
admin/adminPass
ins/adminPass
res/adminPass
About Current Implementation
- Frontend & Backend app using ASP.Net MVC Core
- Getting started on ASP.Net MVC Core here: https://docs.microsoft.com/en-us/aspnet/core/getting-started/?view=aspnetcore-2.1&tabs=macos
- You need use docker to setup database for this application. Read documentation on architecture and backend repo: https://gitlab.com/alta-ski/architecture
- Let us know any problem when you setup both frontend or backend
Individual Requirements
1). Current Widget Capacity Bugs
2). Capacity Flow
Web Browsers Requirements
Your submission must look and work consistently across these following browsers on the latest versions:
- Continue fixing issues on the front-end and back-end of Hoherberg Ski School application
- Focus on Widget Capacity and fixing related solution across the pages
- Continue support unit testing and must not break the application after the updates
Challenge Overview
Hoherberg Ski School web application need build using ASP.Net MVC Core with focus on desktop resolution only. For this challenge we need you updates issues on Web API and the frontend.
Let's discuss any questions you have. See you in the challenge forum!
Technology Stack
ASP.Net MVC Core
HTML5
CSS3
Javascript
Jquery
Deployment environment requirements
localhost
live site
Challenge Assets:
Post your gitlab username on challenge forum to get access to our repo
- Frontend repo: https://gitlab.com/alta-ski/frontend
- Backend repo: https://gitlab.com/alta-ski/backend
Demo site:
http://ec2-3-208-93-68.compute-1.amazonaws.com
admin/adminPass
ins/adminPass
res/adminPass
About Current Implementation
- Frontend & Backend app using ASP.Net MVC Core
- Getting started on ASP.Net MVC Core here: https://docs.microsoft.com/en-us/aspnet/core/getting-started/?view=aspnetcore-2.1&tabs=macos
- You need use docker to setup database for this application. Read documentation on architecture and backend repo: https://gitlab.com/alta-ski/architecture
- Let us know any problem when you setup both frontend or backend
Individual Requirements
1). Current Widget Capacity Bugs
- This widget is placed on top of Reservation Check in page
- [high] Widget Capacity should hold a reserve of instructors based on products
- This is a product buffer that allows the user to gauge capacity and availability on a daily and per specific date basis.
- We need fix calculating availability after the product buffers are applied.
- [high] Fix Widget Capacity to split the availability with this AM/PM
- AM = 8:30AM - 12:59PM
- PM = 1PM - 4:30PM
- [high] Child Availability not returning correct number
- Data Example:
- Instructor: Andy Baker
- Age Range & Skills: 0-99 at level 9
- How do we have 2 child instructor up to level 0? And then 2/0 would mean there’s no availability but there are some instructors including Andy Baker (instructor teaching 0-99 at level 9, in the adult POD but child and adult skill of 9) is available
- Some notes:
- When instructors are a part of PODs, this does not determine what they can teach.
- PODs are just ways to group instructors.
- Instructor teaching age range and associated skills is what determines if they can teach or not - then the instructor must also have the availability (Green with no conflicts on Scheduler page)
- Adult and Child Availability should be based on Age range, not the POD
- Data Example:
2). Capacity Flow
- For this task you need fix current functionalities based on client expected results for Capacity Flow that will be displayed on Widget Capacity: https://docs.google.com/document/d/1GR8tCu4xOqK8rnHTprwGR9INaxHWMZdERi6bR4ZKMR8/edit?usp=sharing
- Check this example based on client testing: https://docs.google.com/document/d/1pUslqqwwOp31h3UWGsLvL2nSc7HJp4PUUxI1akTegrA/edit?usp=sharing
- Your updates will affect other pages in current applications.
- Let us know if you have some questions related to the document.
Web Browsers Requirements
Your submission must look and work consistently across these following browsers on the latest versions:
- IE11
- Chrome,
- Edge,
- Safari,
- Firefox
Final Submission Guidelines
What To Submit?- Patch file of updated solution.
- Challenge winner need submit MR to both backend and frontend.
- Updated README.md (if Any).