We need four web parts with correspondeing four library/list templates for storing links and pictures to be used by web parts (using site columns, 2 content types, lists have at most 7 custom columns; there are 18 columns all together to be created in the project), and a feature to add and set up the solution within a site.
Web part 1: Banner slider big with hover effect (we deliver jquery) + list template for storing banner data
Web part 2: Summary web part for photos and movies (photos with hover effect, videos with loop preview) + list template for storing summary data (two content types - one for movies, one for images);
List templates are to reuse centrally defined columns; altogether there are 18 columns to be defined.
Web part 3: link gallery (presentation similar to tag cloud) + list template for storing link data.
Web part 4: Slider buttons (we deliver jquery) + list for storing buttons data
Feature for seting up the page with web parts and list instances.
For the page layout template, with the corresponding web parts and list templates, there needs to be a feature.
Upon feature activation:
1. Lists based on templates are added to the site. If a given list (based on a list template) already exist, do not add new list.
2. New page is provisioned when the feature is activated, with web parts on it. This page has to have a unique filename in order not to cause any conflicts.
3. The new page will be set to be the welcome page of the site.
We deliver design files (CSS, HTML) for the web parts and a publishing page layout, to be populated with delivered web parts.
The solution is to be run in site collections in the on premise environment - SharePoint Server 2013 (stanard CAL).
We need and NDA to be signed befor the project start, and the IP transfer agreement post delivery.
We expect the solution to be developed on freelancer's environment and delivered as a solution file + VS project files.
ONLY internal column names in within your code.
Use a delivered prefix for internal names.
Use „Sort by” value for sorting items to present them in the web part. If the „sort by” value is inconclusive for two or more items (missing or the same), use internal SharePoint Id of a list item for resolving the final order.
If an item has value „true” in „open in new tab” field, then the url for the item should be opened in new browser tab.
If an item has value „false” in „active” field, omit it in your query (it is not to be presented in the web part).
The „title” and „url” fields are always used as a pair: if you render the title, then the url value is the hyperlink destination.
You can use publishing page layouts and content query web parts if needed.
The publishing infrastructure is in place in the web collection we are designing these for.
If there is nothing to be rendered by a web part, render a message.
Décerné à :
Hello Ela, As agreed I have put my bid request. Please provide all design files including masterpage, page layout and jQuery componenet along with the updated code from your end. Thanks, Ashish