We're currently thinking of doing something of a serious restructuring of our database, but would like to know if what we have in mind is achievable before we go ahead with it. I'm afraid that this post is a little long, so it might be advisable to get a cup of tea before embarking on the task of reading it.
At the moment, we have a pretty standard Actinic product template. We have three levels of sections: manufacturer at the top, then printer type, then the actual product. The products themselves are laid out in rows with several products per page. You can see an example of this at http://mega-office.co.uk/acatalog/Ep...o_Printer.html. From the breadcrumbs at the top, you can see the current structure of our database, with Epson as the parent section, Epson Printer Ink Cartridges as the subsection and then all the products nested within that section.
What we'd like to do is add another level to this structure. In this utopian vision of our database, every product would have its own subsection. Thus, for the above example, the structure would become: Epson > Epson Printer Ink Cartridge > Epson Compatible Picturemate Cartridge and Paper > Actual product component.
That part is obviously quite possible. However, it's not a good idea in terms of usability, since the customer is required to click through to one section more than necessary to be able to buy their product.
Instead, we'd like to have it so that the customer can order from both the product page and the section above. Thus, in the above example, the pages Epson Printer Ink Cartridge and Epson Compatible Picturemate Cartridge and Paper would be pages from which you can add items to your shopping cart.
Having spent hours slaving over a hot stylesheet, I've come up with what I think is quite a nice looking layout for the product rows, which should be viewable at http://printinginks.net/acatalog/Eps...o_Printer.html. The idea is that the product titles would be a link that takes you through to the product page, where further information on the individual product resides.
Phew. So the actual question is: is this at all possible? Can we have cart functions enabled at two different levels like this? And if not, is there a way around it?
Thanks for reading this far. I appreciate any and all input on the matter.
At the moment, we have a pretty standard Actinic product template. We have three levels of sections: manufacturer at the top, then printer type, then the actual product. The products themselves are laid out in rows with several products per page. You can see an example of this at http://mega-office.co.uk/acatalog/Ep...o_Printer.html. From the breadcrumbs at the top, you can see the current structure of our database, with Epson as the parent section, Epson Printer Ink Cartridges as the subsection and then all the products nested within that section.
What we'd like to do is add another level to this structure. In this utopian vision of our database, every product would have its own subsection. Thus, for the above example, the structure would become: Epson > Epson Printer Ink Cartridge > Epson Compatible Picturemate Cartridge and Paper > Actual product component.
That part is obviously quite possible. However, it's not a good idea in terms of usability, since the customer is required to click through to one section more than necessary to be able to buy their product.
Instead, we'd like to have it so that the customer can order from both the product page and the section above. Thus, in the above example, the pages Epson Printer Ink Cartridge and Epson Compatible Picturemate Cartridge and Paper would be pages from which you can add items to your shopping cart.
Having spent hours slaving over a hot stylesheet, I've come up with what I think is quite a nice looking layout for the product rows, which should be viewable at http://printinginks.net/acatalog/Eps...o_Printer.html. The idea is that the product titles would be a link that takes you through to the product page, where further information on the individual product resides.
Phew. So the actual question is: is this at all possible? Can we have cart functions enabled at two different levels like this? And if not, is there a way around it?
Thanks for reading this far. I appreciate any and all input on the matter.
Comment