I've noticed a lot of my custom coding with Radiant is about defining relationships between pages that cut across the tree structure. For example, on http://barefootcoffee.com/, a coffee has one or more varietals. >From a coffee page, you can go to any of its varietals, and from the varietal page, to other coffees that have the same varietal. When they add or remove a coffee from the site, the associated varietal pages are updated automatically.
Likewise, each coffee has several "marks" (organic, fair trade, etc.), and one processing method. To implement these, I've created a bunch of page types that don't have anything to them besides a class name and an association, and some admin page fragments that the customer uses to say which coffees have which varietals, etc. I've been thinking about creating a generic extension to manage these associations. Roughly speaking, customers could define their own page types from the admin UI, and which page types can be associated with each other. (I don't know yet whether I'd actually try to generate distinct page classes and ActiveRecord associations, or just a new page attribute and one big join table.) And the extension would automatically generate select boxes as needed for the page admin UI. Does this sound like a good idea to anyone else? Or a bad one? (Is there a simpler way that I've been missing?) And before I get started... has anyone implemented it already? --Erik Ostrom e...@echographia.com _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
