How would you make this? T-Shirt Catalog

Hello all!

I have one MODx site under my belt and am thinking about converting some of my older sites to MODx. I have site that provide wholesale t-shirt information to dealers. No ordering is involved. Strictly info only. I have written from scratch with a file upload and admin feature with user and admin. But it is cumbersome to maintain. So I am thinking about upgrading it to MODx. But I don’t know how to translate it. I am having a problem with displaying the prices. What is weird is the pricing breakdown. Is is different for each design. Some designs are available in Short Sleeve only, some in Short and Long Sleeve, and Hooded, Thermal, Tank , etc...

[table]
[tr][td]Short Sleeve[/td][td]$10.00[/td][td](48)[/td][/tr]
[tr][td] [/td][td]$9.50[/td][td](72)[/td][/tr]
[tr][td] [/td][td]$9.00[/td][td](144)[/td][/tr]
[tr][td]Long Sleeve[/td][td]$12.50[/td][td](48)[/td][/tr]
[tr][td] [/td][td]$11.50[/td][td](72)[/td][/tr]
[tr][td] [/td][td]$11.00[/td][td](144)[/td][/tr]
[/table]

So my question is how to handle it?

Use 28 TV’s -- (SS48,SS72,SS144,LS48,LS72,LS144,TT48,TT72,TT144,etc...)

Ditto with each shirt type inside a container for each design style?
-Shirts
--MYU05011
---Short Sleeve
---Long Sleeve
--MYU05013
---Short Sleeve
---Long Sleeve
---Tank Top
--MYU05015
---Long Sleeve
---Hoodie
---Thermal


The person maintain the site have no html knowledge. So I can’t just have them paste in a table of prices.

Any ideas?

I would use one document per master product and TVs for each option. That will make it a whole lot easier to update prices and other info than opening and saving tons of sub-documents. Then use a snippet (or a TV widget) to display the available options and prices (if a TV is empty or zero you don’t display it, so you can have all of the TVs for each product and just fill in the ones you need).

Use Ditto to make your catalog list pages, of course.

Ok, so you are suggesting to use multiple TV’s, so if there are 12 total options with 3 prices each... I would have 36 TV’s

As per screenshot

Quote from: bwente at Feb 16, 2008, 02:34 PM

Ok, so you are suggesting to use multiple TV’s, so if there are 12 total options with 3 prices each... I would have 36 TV’s

As per screenshot

You could use 12 TV’s, one for each category (ie: short sleeve, long sleeve...), and input the value in a comma separated list (ie: 48|12.50,72|11.50,144|11.00) then use a snippet to turn this into an associative array and with a loop to display individually.

Quote from: dev_cw at Feb 16, 2008, 04:59 PM

You could use 12 TV’s, one for each category (ie: short sleeve, long sleeve...), and input the value in a comma separated list (ie: 48|12.50,72|11.50,144|11.00) then use a snippet to turn this into an associative array and with a loop to display individually.

That’s a good idea. There is a chance that they could make an error in data entry, but it would be easy to catch.

Or you could try using multi-select list boxes if your option values are relatively standard. Then you could potentially just have one TV and select all of the option/price combos that apply. Whatever seems to make data entry the easiest and least likely to produce errors.

I think the multiple TV’s is probably the way to go.

I am going to try the MangerManger plug-in to see if I can rearrange things to make it easier for them to follow.