You have chosen to sponsor your bid up to a maximum amount of .
This job requires a meticulous and skilled developer with experience in SharePoint, .Net, and web user interface development. The job is to deliver the user interface for a SharePoint product under development, in accordance with the design specification.
In total, this job requires the delivery of six user interface pages, ten single-page dialogs, and two multi-page wizards that contain six pages each.
The solution should be built and tested under both SharePoint 2010 and SharePoint 2013. This requirement will necessitate that the solution is effectively delivered twice – once for each SharePoint version. The two versions should be almost identical, where the differences should amount to no more that referencing the correct version of the SharePoint DLLs, master pages, etc. The behaviour and layout of the pages, dialogs and wizards should be the same for both versions.
All of the pages, dialogs and wizards to be delivered have been designed, with wireframe diagrams and annotations that describe what is expected. The Product Specification document that contains the designs and notes will be shared with the selected developer.
The pages, dialogs and wizards will use a variety of user interface controls, including Repeaters, buttons, data grids, upload controls, calendars, and AJAX panels. A custom tree-view type control will also likely need to be developed to meet the requirements.
No text displayed anywhere in the user interface should be implemented inline – all text must be stored in a resource string library.
The job requires creation of a simple temporary data source, against which the user interface components must function, in order to demonstrate that the user interface "actually works", even though it does not include a business layer.
The data structures which carry data between the data source and the user interface will also need to be developed.
For the purpose of demonstrating successful delivery of this product, the majority of the solution artefacts will be copied via a simple batch file to a sub-folder of the LAYOUTS directory under the 'SharePoint Root'. It is not necessary to create a more formal deployment mechanism or feature. The batch file to copy the various solution files to the appropriate places on the SharePoint server file system must be included in the deliverable package.