Oh, of course this is the way I'm setting things up. You can build
your product detail pages (and even the product list) with standard
magnolia pages which reference a "product" data node. This way you not
only have all the freedom in the world to create as "rich and nice-
looking" pages as you wish, you can also make use of the caching
functionality.
-will
On 06.07.2008, at 17:10, Vincent F. wrote:
Hi,
Personally I would use data module only for storing commercial
details (price, stock quantity) and orders. Relying only on the data
and dms modules would make difficult to compose rich and nice-
looking product pages.
Vincent
- Relying heavily on the data module (and the dms module for images)
- Implementing controller classes and beans to minimize the amount
of scriptlets in the JSPs
- Creating custom magnolia dialogs for the data management (of
course importers would be nice too)
- And also implementing one default set of shop pages (JSPs) to
have the module work "out of the box"
Did this answer your question or did I misunderstand you?
-will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
