MODx Product Browser

  • Posted:
  • Proposals: 2
  • Remote
  • #41412
  • Awarded
Kaspar L. P.
Clipping Path Service P. have already sent a proposal.
  • 1

Description

Experience Level: Intermediate
We require a Product Browser to plug into MODx Revolution as a Component.
The Product Browser should conform to MODx Revolution�s coding standards and use xPDO for database access wherever possible.

All product editing should take place within the MODx environment and have a look and feel that is not too dissimilar to MODx.

It would be beneficial, but not required, for the product editing environment to make use of AJAX where appropriate (eg dragging and dropping products into categories, saving data without reloading pages, etc)

Snippets and other sample code for displaying the categories and products on the front-end of the website should be provided as well.

General Structure

Products should be assignable to multiple categories, which themselves should be navigable in a tree-structure.

Each individual product should be capable of being assigned multiple images, the upload of these should be handled within the product editing environment either using MODx�s file upload utility or a suitable replacement.

Each product should be capable of being assigned multiple option choices, eg for colour, sizes, etc. These options must be completely user definable.

A sample database schema that outlines this structure is attached to the specification.

Data Fields

These are not exhaustive and may be altered based on received feedback.

Categories
ID (auto assigned), Name, URL Alias, Description, Thumbnail Image, Parent Category, Visibility (shown or hidden)

Products
ID (auto assigned), Name, Short Description, Full Description, Price, Weight, URL Alias, Visibility (shown or hidden), Categories, Related Products

Product Images
ID (auto assigned), Caption, Image (path)

Product Options
ID (auto assigned), Name, Range of values

Sample Database Schema - Please see attached image

Other Considerations

We do not currently require a Shopping Cart or any other E-Commerce functionality, although we may need to extend the component to include this at a later date.

Once complete, basic maintenance of the component will be taken over by our in-house team, but we may return to a successful bidder with future work if the business relationship works.

A successful bidder will be asked to sign a Non-Disclosure Agreement in relation to the work undertaken.

New Proposal

Create an account now and send a proposal now to get this job.

Sign up

Clarification Board Ask a Question

    There are no clarification messages.