> Really, sounded like a > custom XML structure would make more sense, like he wants to > extend a knowledgebase very specific to his needs, and > probably starting from the structure of the information > itself would make more sense than starting with (and perhaps > being limited to) the structure of a canned product.
Could you elaborate on this a bit more please? I've been keeping a vague eye on XML but have not as yet found a need for it - or seen where it might improve on what I'm doing. To give you a better idea I managed to find copies of my original static html page attempts to come up with an idea on how this was going to work. You can find examples of what I'm trying to do here - each is a separate product range, with differing amounts of info under each product - the links won't work as they go to our intranet but you get the idea. They all differ slightly depending on what info I had at the time. How this changes once people start to add information or decide they hate the layout is one of those things that will evolve with time - but the basic concept of the 'rangeguide' is there. http://www.waterheating.info/rangeguides/fbm.htm http://www.waterheating.info/rangeguides/express.htm http://www.waterheating.info/rangeguides/hydroboil.htm http://www.waterheating.info/rangeguides/multipoint.htm The major thing I've noted that every sugestion people have made is that the way you edit a page is by choosing it from a list from the admin screens - this will just not work for us. The main thing that drew me to ektron when I first found it was the ability to be browsing the site, see something that needs changing, click the login link at the top of the page and then straight away edit the page you are on. No need to find it amoungst a whole list. I need to make it easy to encourage staff to make a change - asking them to login, go find the page amounst the list and then edit it is not gonna work, they'll think they'll do it later and it will never happen. Back to the original question can you explain how an xml structure would work in this context given the info I've provided above, or how might it improve that? Thanks very much Morkai Ps: he = she :) -- http://cms-list.org/ trim your replies for good karma.
