OMD16 - Online Designer Module

### PLEASE READ THE ATTACHED NOTE as project description here is only limited 4000 characters (not enough) ### This module will be used by at least five (5) distinct web sites that we own; it is very important that it'd be modular so that our existing sites (and future ones) can utilize the same engine. Our sites are developed with asp.net and MS-SQL Server; we will only accept development based off these tools. No FLASH; HTML5 only. Must also be responsive for tablets and phones. Do not worry about any web layout since this is an independent module and should be called up by different sites within their own page layout. Please keep in mind that we will eventually open this module to other interested parties who will pay for this service. In the near term, this will just cater to our own web properties. So, this is very much "Stage 1" of this project. Once "Stage 2" (commercialization) is completed, you will be retained as a consultant to provide additional services and/or help for site integration. So this is not a one-off job. Before you begin, you should reference the following sites (our competitors) and see how they are handling their online designer function. We are not looking for something that's leaps and bounds above what they're doing; we're just trying to establish our own tools. Of the following, the one from [login to view URL] seems to be the best. I'd like to see ours be on par with it. [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] You'll also need to develop a standard set of API so that different sites can communicate with the module. Treat each different site as a "customer" accessing the module so that unique key needed to be assigned to each site. The API will control: - Sessions per month. Number of sessions that each site can create per month. Each "session" is when an end-user places an art on a product. - Return path. While most sites would go into shopping cart after a session is finished, some sites will just return end-user to the image library or product catalog. Once the module is finished, it'll reside on a sub-domain that I'll set-up. All of our web properties that need use the function of our online designer should make API calls to this sub-domain. There's also a "back-end" admin portal where each site will maintain its own data. For now, all five sites will share the same product database; however, each site will be able to determine which product to include on its own site. In the "commercial" version of the future, there will be customers who would want to use our product database, or create/upload their own. The commercial version will be at a later stage and is not within the scope of this present project. In addition to the product database in the admin portal, each site will also be able to access each saved design session. Since all the art files uploaded by end-users are saved on the same server as the module, each site will need to retrieve the uploaded artwork file and find out how the end-user wanted the art positioned on the product. ### PLEASE READ THE ATTACHED NOTE as project description here is only limited 4000 characters (not enough) ###