Wissenkarten Projekt - Serve the prototype with the back end

Guten Tag Community. Willkommen auf Wissenkarten Projekt.

Note: We wish to close the challenge as soon as possible as we need the solution quickly. Hence, please note that we may close this challenge by 30th March if we don't get valid submission by then.

 

Project Overview
Wissenkarten Projekt is an application that provides many services to the end user is the form of "knowledge cards". Think of these as widgets with additional functionality associated with them.

 

Challenge Details

We have developed a prototype for the application.

We have also developed the back end for the application. Currently it only contains the weather and wolfram alpha cards.

 

This challenge requires you to carry out the following:

1. Take the prototype and merge it with the back end.
2. In the process, ensure that you respect and follow the folder structure. Don't randomly copy files.
3. The back end contains tests. They should continue to run successfully even after the merge
4. The back end also contains a demo user interface. You need to remove this and replace it with the prototype.
5. The prototype contains just one page. This page contains the cards and they are displayed in a carousel (use the left and right arrow keys to slide them). After the merge there should be no change in their behaviour.
6. You can run the back end using the $ grunt command. This will start the server and you can access the demo user interface at localhost:4444. After the integration, we should be able to access the prototype at that location by running the same command.
7. You DON'T have to map the cards with the back end.
8. The front end uses slick carousel. However, it also contains references to the old carousel - swiperjs. Remove any references to this.
9. Finally, the prototype directly makes use of javascript libraries and css stylesheets. Instead, couple them all into a single bower.json file (replace the one in the backend) and let this be the installation procedure. Update any links in the process.

Simply put, display the prototype using the back end server. You don't have to make the client speak to the server other than displaying the HTML files.

You need to carry out some housekeeping to remove unwanted code.

Final Submission Guidelines

Submit the entire application in a zip file. Note that the application used package.json and bower.json to install the dependencies so don't include them in your submission.

The winner will be asked to push their changes to our gitlab repository.

Before submitting, make sure you check your submission against the 9 points mentioned in the challenge details.