Ohio - Deferred Compensation UI Prototype to ASP.NET Conversion Challenge - Part 2

Welcome to Ohio - Deferred Compensation UI Prototype to ASP.NET Conversion Challenge - Part 2.

This challenge is focussed on converting the existing UI prototype to an ASP.NET MVC application. This is part 2 of our series of challenges to build this ASP.NET prototype. Please read the spec for part 1 to familiarise yourself with the scope - the code from this challenge is provided in our repo and MUST be used as a starting point for your submission. Have any questions, let’s discuss in forums!

Scope:

There are 2 main parts to this challenge.

• Integrate all screens from UI Prototype Challenge 3 into the existing ASP.NET prototype. The UI prototype code for these screens is available in part3 branch in the repo.
• ���Integrate all screens from UI Prototype Challenge 4 into the existing ASP.NET prototype. The UI prototype code for these screens is available in part4 branch in the repo.

All screens for tablet view (portrait) are also implemented for mobile storyboard. You can find the Marvelapp links in the forums

If you have any doubts about the scope/ screens involved, please post in the forums.

~

TECHNOLOGIES

• Visual Studio 2015/ 2017

• ���HTML 5

• C#

• JavaScript

• CSS 3.0

• Bootstrap 3.3.6

• JQuery 2.2.0

 

CODE REQUIREMENTS:

ASP.NET

- You may use Visual Studio 2015 or 2017

- MUST use ASP.NET Framework 4.6.2, ASP.NET Core is NOT ALLOWED

- All source code should be well commented

- Use the same namespace as defined in existing code

- All Javascript & CSS files must use bundling

- Please use a templating engine - you are free to use Razor Pages or another wrapper framework such as RazorEngine - if you have any other suggestions on how to handle the view layer, let us discuss this in the forums.

- Follow guidelines in the existing code

- Refresh only the portions of page that need to be changed. Do NOT refresh full pages if they contain static content

- Use POST actions with proper models in controllers to handle data that is submitted by user (already followed in existing code)

- MUST use bundling (already followed in existing code)

- Follow existing prototype UI validations wherever needed

- Use Ajax to show/ hide page elements as needed, full postback is NOT required

CSS3

- Provide comments on the CSS code. We need CSS comments to give a clear explanation of the code usage. The goal is to help future developers understand the code.

- Please use clean INDENTATION for all CSS so developers can follow the code.

- All CSS naming should not have any conflicts.

- As possible use CSS3 style when create all styling.

- Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to lay out your page. Only use table tags for tables of data/information and not for page layout.

Javascript

- All JavaScript must not have a copyright by a third party.

- It is fine to use GPL/MIT/Open Source code.

- You are encouraged to use your own scripts, or scripts that are free, publicly available and do not have copyright statements or author recognition requirements anywhere in the code.

Browsers Requirements

- IE 10, 11

- Firefox, Chrome, Safari, Microsoft Edge latest version

- Chrome / Safari mobile browsers

Final Submission Guidelines

- Submit the Visual Studio 2015/ 2017 project implementing all existing UI prototype screens

- Provide a deployment guide providing configuration and verification information for your submission

- Provide a demo video of your solution- Provide an Azure URL hosting your working submission - this is a MUST and submissions will be scored down for not doing so.

- Winner will be asked to raise a merge request to the repo