Custom Tshirts

Hey Matthew,

I think the most common scenario would work like this:

1. A visitor to the site would enter a web address in the browser and request the page to build a shirt.
2. Some server-side code (like PHP) would get the list of all the options for a shirt (probably from a database like MySQL) and it would generate the page that displays the shirt builder will all of those options. It would send that page back to the browser. (That page would include all the JavaScript code that would get executed in the next step.)
3. The shirt builder would load in the browser, and the visitor would be able to interact with it. All the clicking and dragging would execute JavaScript code (which might use the jQuery framework) to build the shirt without refreshing the page.
4. When the visitor finished building the shirt, the visitor would click an Add to Cart button. That would submit a form back to the server, sending it all the information about the built shirt.
5. Some more server-side code would get the information about the shirt and add it to the visitor's cart.

Does that all make sense?

(Of course, you could also use Ajax at various points in steps 3-5 to save the shirt configuration as the visitor builds it [instead of waiting until they say they are finished] and to add it to the cart, but I think the way I've laid it out is probably common enough.)

Like this? @randyhoyt @andrewchalkley

Randy Hoyt Andrew Chalkley Please read above. Thank You.