Front-end developer for long term challenging HTML/CSS/JS tasks

This job will be the beginning of a long term cooperation. Please include your GitHub account. Pixel perfect implementation, no laggy scrolling, optimized/compressed assets and no errors in inspector are a must. To begin with, I have this small project where I need you to create a single web page that will fulfill the following requirements: - Be responsive, but not for phone screen size (Twitter Bootstrap v3.3.4) - Be rendered from JSON objects - Consist of three main parts: top slider, details preview (design materials and invision prototypes are attached, ignore the charts) - Top slider and details preview parts should be independent components that can be re-used in the other pages Definitions: - Flow screen: The application screen (e.g. Home screen, Product search screen, checkout screen, etc.) - Flow: The sequence of the screens that the user navigated through, with the last actions triggered, if available - Screen exit touch: The last touch event on the screen before navigating to the next screen. If missing, means it’s auto transition Top slider (Flows list): - Here is the JSON sample data based on which the slider should be rendered: [login to view URL] - The slider should dynamically load cards when you scroll or navigate through arrows and reach the right edge (lazy loading). - A connecting line between slider and details grows or shrinks accordingly and the tip moves when you scroll. If the card is out of viewport, then hide the tip of the line. - To see the full list of screen names of the flow hover on the slider card. If screens name list is too large show vertical scroll. - Each card (flow) in slider has the following: -- The ordering number (#1, #2, #3, ect.) -- Title, which should take maximum 2 lines. If it’s too long, then show ... -- Start thumbnail, end thumbnail. If the flow contains 1 screen, then we show Start thumbnail twice. If one of the thumbnails has landscape orientation, then we rotate it. -- Screens count Details (Selected flow details): - Here is the JSON sample data based on which the details preview should be rendered: [login to view URL] - Each screen in details has the following: -- Title on top, max 2 lines -- Duration at the bottom -- Exit Touch - Whey user clicks on screen title, it transforms to an input where user can edit the name of screen and save it by pressing save button or cancel - To navigate to previous/next flow click on corresponding arrows - Flow navigation is drawn snake like with arrows between screens showing the navigation direction. The arrows should be vertically and horizontally center aligned. The text boxes between screens (above arrows) are the events triggering the navigation. There are three possible events. -- An exit touch - when the user taps on specific button to navigate to the next/previous screen -- A screen rotation - when the user rotates the phone. In this case the ExitTouches property in details JSON will be an empty array and the two screens will be the same only with different Orientations. -- A screen transition - when the navigation is done without any user interaction. In this case the ExitTouches property in details JSON will be an empty array and the two screens will be different. - Flow Details should be responsive, if there is not enough place for the screen, pass it to the next line. Invision prototype: [login to view URL] PNG mockup: [login to view URL] PSD: [login to view URL]