<tom wrote> Basicaly you end up with a massive range of different sitemaps - >> almost one for each phone - whereas what you really want is a single >> sitemap and rules to define what pages are shown to different groups >> of phones. >> >> b) Is there another way to approach this problem that results in a >> solution without massive customisation to the CMS? <>
As discussed yesterday on the phone Tom, I have been trying to work out how to solve this and I think the solution is to look at the problem from different angle It looks to me that the most optimal software solution could be to build a interface that reads the preferences off the phone and matches compatible data/information dynamically each time a user logs onto the system. This 'filter plug' can be adapted to work onto any CMS you like, and can be easily upgraded as more Phones come out etc. So no sitemaps. It is a |A approach. I'd be curious to hear how you solve it otherwise Cheers Paola Di Maio Intelligent Systems Design -- http://cms-list.org/ trim your replies for good karma.
