Thursday 22 May 2008 1:41:40 am
That's great for having a Contact page with details on it that you can republish as a whole page - I'm sure lots of us do exactly that. Also you can fetch the attributes of the object (e.g. Sales Telephone Number, address etc) by reference to the object's node id using template functions etc. This is too technical for end users though who don't know how to use the template language - they want to be able to enter the information using an XML field and still have it updatable. How about creating classes for telephone numbers, addresses etc., and publishing them as objects in their own right (organised into an appropriately named container class), these can then have embed-inline/inline templates etc. that make them appear nicely formatted when dropped into an XML field by the end user. This gives more flexibility in terms of which bits of the data are shown where. Then it would be relatively straightforward to create a new object class and associated templates, which accesses these classes (and therefore remains up to date when contact details get changed) using the template language as your Contact Page which can then be republished wherever you like. Or is there another way?
|