All of the pages have been designed as layered PSD files. Ideally they should be tableless, where possible and the final HTML/CSS design should include a CSS framework such as (Bulma or Kube). We would prefer not to use Bootstrap in order to keep load times to an absolute minimum. All are required to be produced as Blade Templates for use on a Laravel 5.5 framework website. The templates should have the common header/footer area's which are separated off into separate templates for ease of maintenance.
Of the eight PSDs, three are straight forward conversion to HTML/CSS Blade Templates. The other five, all are straight forward conversions, but certain area's of the page will require the data to be updated every 20-30 seconds. Our aim is to ensure that the minimal amount of data is returned each time, as some users may be on mobile devices with GPRS, 3G or 4G connections - so we are looking to create some from of check that can be sent to the server and data is only returned and updated if it has changed.
There are times however, when the frequent updates need to be turned off - either the data is complete for the day, or the updates haven't started yet, so there is no point in continually polling for updates when we know in advance none are available. This should be taken into account. The data passed to the template from the Laravel Controller will include a 'liveUpdates' variable with 'N', 'A' or 'L' values, corresponding to (N)o live updates, in which the template should switch the updates off, (A)dvance updates in which case it should be checked every 5 minutes and (L)ive updates in which case they should be updated every 20 seconds. Separate values 'liveadvance' and 'livestart' will also be passed. Both will contain time values - the liveadvanced field will give the time that the page should automatically start the (A)dvance updates, while livestart is the time the page should move to the (L)ive frequency updates. These fields are only given if the original 'liveUpdates' value from the controller is 'N' or 'A'. At some point each day, one of the live updates may also return a message to stop the frequent updates, which should move the page to 'N' mode.
All updates should call a specific controller within the Laravel application to retrieve and process the necessary data.
On two of the pages, there is also the requirement given a particular specific response from the frequent update to change part of the page that is not normally included in the frequent updates.
Conversion of EIGHT (8) PSD files to HTML5/CSS3 Laravel Blade Templates, including splitting out the common headers/footers etc. CSS should comprise of one file where possible.
No core PHP work in the Laravel Controllers is included.
Regular uploading of progress to a Bitbucket account is a requirement of the work.
We will work with the winning developer to create the required number of backend database calls in order to return the necessary data from the database.
Extra notes: Its is our intention to award this project around the second week of December - please bear this in mind. The requirement is to have the work completed and the pages working BEFORE the Christmas period. If this causes any problems at any time, it is a requirement that this is brought to our attention as soon as known.