We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34120
    • 236 Posts
    I’m building a catalogue site which will be quite heavy on technical data and I need some advice on how to approach this. I’ve built a few modx sites now and normally I create a resource/page for each product item and then use ditto to list these etc. This current project however is a bit bigger and I’m not sure if this is the best approach. Below is the structure, I don’t have any problems with this bit, I’m just posting it for context.
    Products
    => Category
    => => Sub category
    => => => Product 01
    => => => Product 02
    => => => Product 03
    


    I’ve attached a screen shot of the data. Using my usual method I would create a resource/page for each row of the data, this seems quite long-winded though for this amount of items. A possible alternative might be create a product with variants eg.size etc.

    I hope this is clear, I’ll be using Revo rc1 but I’ve posted here as it’s more of a general question about how to structure data within MODx.

    Similar questions have been asked here but there hasn’t been much response.
    Hope someone can offer some advice.
    Thanks
      • 34120
      • 236 Posts
      Just thought I’d follow this up. I decided the best way to figure this out was to get stuck in and start building. I’ve used my usual approach and created a resource for every row of product data. I’m populating the site by importing csv data into the database to speed things up.

      I had a quick look in the sticky about MODx page limit, I need to read over it in full. There was mention of pulling data from a custom database table rather than creating all the individual pages. I think this is what I was getting at in my first post, I don’t really think this is necessary though for the size of the site I’m currently working on.